Work from your tools

Platform MCP server

Connect any MCP client to Praxen Inc. and query telemetry, the topology, code and issues from your editor, with writes only when you opt in.

Praxen Inc. runs a Model Context Protocol server at https://mcp.getpraxen.app/mcp over streamable HTTP. Connect any MCP client and your agent can query telemetry, the topology, code and issues without leaving your editor.

What it does

The server exposes the Praxen Inc. REST API and the same agent tools Praxen Inc.'s own agents use across every connected provider in the catalog. The server card at https://mcp.getpraxen.app/.well-known/mcp lists every tool. Once connected, ask your agent something like "Use Praxen Inc. to show me the error rate for the service this branch deploys, over the last hour."

Tools

Tool	Description
`search`	Queries the Praxen Inc. OpenAPI specification from a small async function that runs in a sandbox against a resolved copy of the spec. Read-only.
`execute`	Calls the REST API through `codemode.request({ method, path, query, body })`; the API enforces your credential's scopes on every call.
`searchTools`	Lists the agent tools your workspace and credential can use, with their input schemas. Call it first.
`runTool`	Runs one agent tool by its exact `toolName`, with its arguments as a nested `params` object.
`runCode`	Chains several agent tools in one call from TypeScript written against a `tools.<name>(args)` namespace.
`reportFeedback`	Reports friction with the server to the Praxen Inc. team, with the client, session id and workspace attached so the team can reproduce it.

Authentication

OAuth is the default: the server is an OAuth 2.0 provider with dynamic client registration, so a client that connects with no headers opens your browser to approve it and sign in to Praxen Inc. An OAuth session can span several workspaces, so pass workspaceId (id or slug) on agent-tool calls.

Where a browser sign-in is not possible, such as continuous integration or a remote machine, open Settings > Coding Agents and click Create API key: the key carries every read scope the MCP tools check, is shown once and starts with sk_. Send it as x-api-key: <key> or as Authorization: Bearer <key>; a key is bound to one workspace, so workspaceId is optional.

Install in your editor

Claude Code, Cursor and Codex can install this server together with the Praxen Inc. skills as a plugin. To register the server on its own, add it to your client:

Terminal

claude mcp add --transport http praxen https://mcp.getpraxen.app/mcp

opencode.json

{
  "mcp": {
    "praxen": {
      "type": "remote",
      "url": "https://mcp.getpraxen.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.praxen]
url = "https://mcp.getpraxen.app/mcp"

If your build lacks streamable HTTP, bridge with npx mcp-remote https://mcp.getpraxen.app/mcp.

.cursor/mcp.json

{
  "mcpServers": {
    "praxen": {
      "type": "http",
      "url": "https://mcp.getpraxen.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "praxen": {
      "type": "http",
      "url": "https://mcp.getpraxen.app/mcp"
    }
  }
}

Each client opens a browser to sign in on first use. To use an API key instead, add an x-api-key header to the same entry through your client's header setting, such as --header "x-api-key: YOUR_API_KEY" for Claude Code or http_headers for Codex.

Writes

Agent tools stay read-only until the session sends x-praxen-allow-writes: true with a credential that carries the agent_tools:write scope. A safety model screens every write and clients that support elicitation ask you to approve each one; see Reads by default, writes behind a gate.

Limits

Each credential can make 600 requests per 60 seconds. Requests past that budget receive a rate-limit response until the window resets.

Work from your tools: how the MCP server, the CLI and the plugins fit together.
Plugins: install this server, the docs server and the skills in one step.
Docs MCP server: the separate server that lets your agent search and read these docs.
API keys and OAuth: scopes, key management and OAuth clients.
MCP integration: let Praxen Inc.'s agents call tools from a server you run.