MCP server

Doxynix runs a Model Context Protocol server next to the API, so an agent can query a workspace with the tools the in-app agent uses.

Endpoint

https://doxynix.space/api/mcp

The path is relative to the app root, so a deployment on another host serves the server at ${APP_URL}/api/mcp. The transport is streamable HTTP; both GET and POST are accepted.

Authentication

Send the key as a bearer token:

Authorization: Bearer <API key>

The key must have the MCP scope, or FULL, which includes it. Create one on the API keys page and give it only the scope the agent needs.

Client configuration

Add the server to the MCP client config. HTTP-transport MCP clients generally accept a server entry with url and headers; check your client's config format:

{
  "mcpServers": {
    "doxynix": {
      "url": "https://doxynix.space/api/mcp",
      "headers": {
        "Authorization": "Bearer ${DOXYNIX_API_KEY}"
      }
    }
  }
}

Keep the key in the environment and interpolate it, as above, instead of pasting the secret into a file you might commit.

Tools

The server exposes the agent's tools that can run without an interactive chat, minus the six mutation tools that change account or repository state:

• applyFix
• createApiKey
• revokeApiKey
• updateApiKey
• deleteRepository
• openPullRequest

Everything else is available, including triggerRepositoryAnalysis, stageFile and markNotificationAsRead, so the server is not read-only. Staging a file writes to the Doxynix workspace, not to your repository; publishing still means opening a pull request you review.

What you can ask

Typical prompts map to a few tool calls:

• Inspect repositories, branches, trees and files.
• Read the latest analysis, its metrics and the generated documents.
• List pull request findings and existing review comments.
• Search the workspace for a symbol, a file or a past finding.
• Trigger a new analysis and poll it until it finishes.
• Stage a generated document or fix so it is ready for a pull request.

Scope

The key is bound to a single workspace. Every tool call runs inside that workspace, so an agent can only reach its repositories, and it cannot escalate by passing a repository id from another workspace.

Troubleshooting

• 401 Unauthorized — the Authorization header is missing, malformed, or the key was revoked.
• A tool fails with a permission error — the key has only CLI or the workspace role is too low for that tool. Re-issue the key with MCP or FULL.
• The client connects but lists no tools — it is speaking to the wrong path. The endpoint ends in /api/mcp, not /api.