Get a teamspace API token
Sign in to NEXT.
Open Teamspace settings → API tokens and create a new API token.
Copy the generated token and provide it to your MCP client in the
Authorizationheader as:Authorization: Token <api_token>
Teamspace API tokens are scoped to a single teamspace: they only grant access to the recordings, highlights, clusters, and workflows inside that space. You can generate multiple tokens (for different teamspaces or purposes) and rotate or revoke tokens anytime from the same settings page if you suspect they’ve been exposed.
Transport and protocol support
The hosted MCP server is available at:
https://mcp.eu-west-1.nextapp.co/stream
It is delivered through AWS API Gateway’s streaming HTTP interface:
Clients must support HTTP response streaming to consume results progressively.
Server-Sent Events (SSE) are not available from the hosted endpoint.
Self-hosting an MCP server (optional)
For most customers, the hosted MCP server at https://mcp.eu-west-1.nextapp.co/stream is the easiest and recommended way to connect.
If you need features that the hosted server does not provide (for example, SSE or custom transport options), you can run your own MCP server. As a starting point, you can look at the open-source implementation published here: https://github.com/Collaborne/mcp-server.
Client integration checklist
Start with
tools/list: Every session should begin by invoking thetools/listtool. The hosted MCP server exposes capabilities based on your teamspace configuration, and listing tools ensures the client knows which operations are currently available.Secure tokens: Store teamspace API tokens safely. They carry the same access that your teamspace provides and should be treated like any other credential.
Test setup: Use the official MCP Inspector to validate connections, list available tools, and run test calls before integrating into production workflows.
FAQ
Q: What is MCP?
MCP stands for Model Context Protocol. MCP is an open standard that give AI agents (eg. Cursor code editor) a consistent way to connect with tools, services, and data no matter where they live or how they're built.
Q: What is an MCP Server?
An MCP server is a program hosted on a server or in the cloud that exposes capabilities for AI agents to use via MCP. MCP servers can provide AI agents with access to new data sets or other tools that they need.
Q: Is my data secure?
Yes. All traffic is encrypted via HTTPS, and tokens scope access to a single teamspace. Only data from the teamspace linked to your token is accessible.
Q: Can I connect multiple NEXT teamspaces?
Yes. Each teamspace requires its own API token. Configure a separate MCP connection for every teamspace you want to connect.
Q: Are all NEXT features available via the MCP server?
Generally yes - the same MCP server powers Threads inside the NEXT UI.
However, some features cannot be exposed due to limits of the MCP protocol or typical client implementations. Most notably, requests are capped at ~30 seconds, which is shorter than what dynamic cluster generation requires. As a result, cluster generation is not available via the hosted MCP server.
Q: Do I need to update the server myself?
No. The hosted MCP server is maintained by NEXT and always runs the latest version. If you self-host the open-source server, you’ll need to keep it up to date manually.
Q: Can I connect from clients that don't support Authorization headers?
Some services don’t yet allow setting a custom Authorization header. Since our hosted MCP server requires an Authorization: Token ... header, those services cannot connect. In that case, you need to use a client that supports custom headers or self-host the MCP server.