Skip to content
Oakstack logo

Oakstack MCP server

Which MCP servers are Oakstack's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Oakstack

Whose server it is
  • Registry namedev.oakstack/oakstackverified in the MCP registry

The registry name sits under oakstack.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Staterequires sign-inchecked 2026-10-27

On 2026-10-27 the server answered and asked for a sign-in with a Oakstack account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "oakstack": {
      "type": "http",
      "url": "https://oakstack.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http oakstack https://oakstack.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://oakstack.dev/mcp as a custom connector in the settings.

The first time it connects, the client opens a Oakstack sign-in.

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.