Back to all tools
Project recordAI & developmentLiveUpdated

Rank-in-Maps MCP Server

Connect Claude, ChatGPT, or any MCP client to your Rank-in-Maps workspace.

The Rank-in-Maps MCP server exposes your workspace's OKF Second Brain and public product docs to any Model Context Protocol client over Streamable HTTP — the same endpoint the in-app AI workspace uses. Standard clients like Claude Code, Cowork, and Claude Desktop connect with a normal OAuth sign-in; no token to copy or config to hand-edit.

What is the Rank-in-Maps MCP server?

The Rank-in-Maps MCP server is a Model Context Protocol endpoint (Streamable HTTP, stateless) that lets AI clients — Claude Desktop, Claude Code, Cowork, MCP Inspector, or your own scripts — read and write a workspace's OKF Second Brain data and search public product documentation. It implements MCP's standard OAuth discovery flow backed by WorkOS Connect, so compatible clients authenticate with a normal browser sign-in rather than a hand-copied token; older or non-interactive clients can still send a WorkOS bearer token manually. Every tool that touches a location is gated to that location's owner, and the launched tool surface is currently a small, deliberately scoped set — public docs search plus the OKF Second Brain read/write tools — with more of the registered tool catalog rolling out progressively.

Overview

The server exposes your workspace's data over the Model Context Protocol so any compatible AI client can query it directly, instead of you copy-pasting context between tools.

It's the same endpoint the in-app AI workspace uses, reachable on the Convex HTTP site (not the Convex backend), and it speaks stateless Streamable HTTP — no session IDs to track between calls.

Only a subset of the full tool registry is switched on today: public product-docs search plus the OKF Second Brain read/write tools. The rest of the catalog is registered in code and rolls out progressively as it's ready.

Key features

Standard OAuth connect

Claude Code, Cowork, and Claude Desktop discover and complete authentication on their own via MCP's OAuth flow backed by WorkOS Connect — no token to copy.

OKF Second Brain tools

Bootstrap a location's Second Brain, write customer review evidence, append audit results, store generated content, and read back structured entities and recent actions.

Public docs search

Search and read public-tier product documentation without needing a location — useful for any logged-in client that just wants answers about how the product works.

Manual bearer token fallback

Clients that don't yet support MCP OAuth discovery can still send a WorkOS access token directly as a Bearer header.

Architecture

TransportStreamable HTTP, stateless — no session IDs persisted across calls, JSON responses (no SSE framing required).
AuthMCP standard OAuth (RFC 9728 discovery + PKCE) via WorkOS Connect for compatible clients; manual WorkOS bearer token as a fallback for the rest.
HostingServed from the Convex HTTP site (`.site`), not the Convex backend (`.cloud`).
Access boundaryEvery tool that touches a location checks that the authenticated user owns it; unauthorized calls return Forbidden.
Model Context ProtocolConvexWorkOS Connect

Looking for another tool?

Browse all tools