@p7ntech/mcp

@p7ntech/mcp

Connect an MCP client to your Platform7n workspaces — 7n.chat (chat), url.dog (links), and wsid (tasks). One-click OAuth; your access never exceeds your own permissions, and the token is revocable in Settings → Connections.

Install

Desktop Extension (one click)

Install the .dxt (built from this package's manifest.json) into a client that supports Desktop Extensions (e.g. Claude Desktop). It opens a browser consent screen on first use.

Any MCP client (config)

Add a stdio server that runs this package:

{
  "mcpServers": {
    "platform7n": {
      "command": "npx",
      "args": ["-y", "@p7ntech/mcp"]
    }
  }
}

The default endpoint is the app-neutral platform host https://api.p7n.tech/mcp. Point it at staging or a specific cell with an argument or PLATFORM7N_MCP_URL:

"args": ["-y", "@p7ntech/mcp", "https://staging.api.p7n.tech/mcp"]

Staging is not published to the registry and is access-gated — it only issues MCP tokens to allow-listed accounts. It's for the platform team's testing, not public use.

How it works

The platform's MCP endpoint is a streamable-HTTP server that is its own OAuth 2.1 Authorization Server (ADR-023). This package is a thin bridge that delegates to the standard mcp-remote: it discovers /.well-known/oauth-authorization-server, runs the PKCE browser consent, and proxies stdio ⇄ the remote endpoint. The issued token is audience-restricted to /mcp and hard-scoped to the workspaces you grant (#430) — it cannot be replayed against the REST API.

Tools

discover, list_workspaces, whoami, and list_/get_/create_/update_/delete_<resource> across the resources you can access.

Publishing (#440): this package is the npm + Desktop-Extension wrapper. The public MCP-registry listing (server.json, namespace tech.p7n/platform7n) points at the prod remote api.p7n.tech/mcp. Full publish steps are in docs/ops/mcp-distribution.md.