⌘ SchemaMap

MCP, REST and AI integrations

Connect ChatGPT, Claude and Codex: public contracts, OAuth, tested compatibility, channels and background-reply limitations.

SchemaMap 0.14.0 · Updated · The editor uses Russian UI labels, shown as written.

    REST and MCP share services

    REST is the primary API; MCP calls the same application services. Swagger, OpenAPI JSON, MCP reference and tools/list schemas are generated from current definitions. Read exact arguments from those contracts rather than an old chat reply. References are public; area operations require authentication.

    Connect an assistant

    1. Open the user menu → «API и MCP» (API and MCP). Select the area and minimum permissions.
    2. For an OAuth client use https://dbmap.anticheckers.com/mcp, sign in and approve required scopes.
    3. For REST/Bearer create a separate key. Keep it private; examples use YOUR_API_KEY.
    4. Start with areas_list and schema reading. Before writing, read the current revision and use mutationId for safe network retries.

    Image reading needs a separate scope. Existing OAuth consent does not acquire new permissions automatically. Source-code access is granted separately within the agent’s environment.

    Tested compatibility

    Local Codex CLI was tested with codex-cli 0.164.0; the research Linux worker requires Node.js 22+. Automated checks cover HTTP, OAuth, MCP SDK, tool catalogs, ACLs and textual JSON responses. They do not prove a personal ChatGPT/Voice catalog refresh or proof retention after context compaction in a particular Claude client.

    ChatGPT and Claude can connect as MCP/OAuth-capable clients where that feature is available in their product. Inspect the actual tools in your client. For a stale catalog, use the upgrade diagnostic. A server test does not guarantee a particular client, plan or voice mode.

    Channels and background replies

    Each chat and worker needs its own channel. Since 0.13.0, the server channel has no deadline (expiresAt:null), but the client retains its proof. Explicit revocation and connection permissions still apply. Lost proof does not authorize taking over another chat’s channel.

    Discussions and research tasks require a configured responder. The downloadable worker reads permitted sources and responds; registration alone does not launch a process. A web chat reads available replies while active and continues on the next user request. Automatic waking of a finished web chat is not advertised.