Skip to main content

NEXT Configuration MCP Server

The NEXT Configuration MCP Server lets MCP-compatible clients such as Claude and Codex inspect and configure a NEXT teamspace. You can use natural-language instructions to create tagging agents and workflows while NEXT validates the configuration before saving it.

Installation​

  1. Create a new API token in NEXT

  2. Run the NEXT Agent installer (Claude Code, Codex, Cursor, Antigravity, etc):

    npx @nextappco/agent setup

    The installer detects supported AI agents such as Claude Code, Codex, Cursor, and Antigravity, and configures the NEXT MCP server and Agent Skill. When prompted, provide the API token created above.

  3. Restart your AI agent if it is already running

note

Teamspace API tokens are scoped to one teamspace. The MCP server cannot read or change configuration in another teamspace. Create separate tokens for a different teamspace, and run the NEXT Agent installer again.

Endpoint and transport​

The hosted Configuration MCP Server is available at:

https://rest.eu-west-1.nextapp.co/config-mcp

It uses the MCP Streamable HTTP transport in stateless JSON-response mode:

  • Send MCP requests with HTTP POST.
  • Set Content-Type: application/json.
  • Set Accept: application/json, text/event-stream for compatibility with MCP clients.
  • The endpoint does not use persistent sessions or a standalone SSE connection.

Your MCP client should send the API token on every request.

Available capabilities​

The Configuration MCP Server lets AI clients inspect and manage configuration within a NEXT teamspace.

It currently supports:

  • Tagging: Inspect and configure automatic AI- and search-based tagging of memories.
  • Workflows: Inspect, design, validate, and create NEXT workflows.

The server provides validation capabilities so clients can check proposed configuration before making changes.

Available tools and their authoritative descriptions and schemas are exposed through MCP tool discovery. Clients should use tools/list rather than relying on documentation for individual tools or parameters.

Troubleshooting​

  • HTTP 401: Check that the client sends Authorization: Bearer <api_token> on every request. Confirm that the configured token has not been revoked and belongs to the intended teamspace. Restart the MCP client after changing an environment variable or token in its configuration.
  • A validation tool returns errors: Let the client correct the reported fields, connections, or references, then validate again before creation.
  • A creation tool reports a server error after validation succeeds: Do not repeatedly submit the request. Report the returned error code and message to NEXT support so the server-side failure can be investigated.