Browse documentation

Connect a Coding Agent via MCP

Connect a Streamable HTTP MCP client to the correct Reqode project, branch, and subsystem.

Before you start

Use a Reqode account with access to the project and a coding agent that supports remote MCP servers over Streamable HTTP. You'll need the MCP URL for the subsystem and your personal MCP token. Treat the token as a credential and store it in a secret manager or your client's credential store.

Find the connection details

  1. Open your project and select the branch the agent will work with.
  2. Open Architecture, select the subsystem the agent needs, and open its MCP tab.
  3. In MCP for Coding Agents, copy MCP URL and check the listed branch context and subsystem.
  4. Use your personal MCP token. If your account has no token yet, use Manage MCP token in the connection settings and issue one.

Configure your coding agent

Add the copied URL as a Streamable HTTP server. Configure bearer authentication using the personal token. Clients that ask for headers accept an Authorization header with the value Bearer <personal MCP token>.

For Codex, set REQODE_MCP_URL to the URL you copied and provide REQODE_MCP_TOKEN to the Codex process through your usual credential workflow. Then add the server.

codex mcp add reqode \
  --url "$REQODE_MCP_URL" \
  --bearer-token-env-var REQODE_MCP_TOKEN

Verify the connection

Start a new session in your client and ask it to run get-app-manifest on the configured Reqode server. Check that the response describes the project and subsystem you selected. If the tool is unavailable, check the server name in your client, the copied URL and branch, and whether the client process can read the token.

Once the connection works, give the agent a requirement key from your project. Ask it to summarize the acceptance criteria and list the linked specifications.

Contact Us

Fields marked * are required.

0 / 5,000

Prefer regular e-mail? info@reqode.com