knowledge-mcpSign in

Your coding agent
knows our products.

Claude Code, Codex, Cursor and Claude Desktop all speak MCP. Install knowledge-mcp-connector, paste your token into your agent’s settings — that is the whole configuration — and your agent answers from approved product knowledge, pinned to the GitLab source of truth and limited to the products you are allowed to see.

npm i -g @atbas/knowledge-mcp-connector

Needs Node 22 or newer. Already installed? The same line updates it. Clients with remote MCP support can skip the connector and call the endpoint directly.

See the tools

No self-registration. An administrator creates your account and emails you a one-time set-up link.

payments-api — claude codesnapshot a91f3c2
$ npm i -g @atbas/knowledge-mcp-connector
$ knowledge-mcp-connector doctor
✓ token found in KNOWLEDGE_MCP_TOKEN · endpoint reachable · 7 tools
Added knowledge · stdio · 7 tools

> can the wallet refund a prepaid-card top-up partially?
● dgmcp_resolve("refund prepaid top-up") → 3 candidates
● dgmcp_capability_status(id: "digital-wallet.top-up.refund-to-source") → partial
✓ Prepaid cards support full refunds only — cited refund-to-source#supported-funding-sources @ a91f3c2
Example session: a developer asks Claude Code about a product capability.

Or paste this into your agent

Include your token in the same message if you have one; otherwise the agent will ask.

Install the Knowledge MCP server in this coding agent.

Run exactly: npm i -g @atbas/knowledge-mcp-connector
Needs Node 22 or newer. Do not use npx, pnpx, bunx, pnpm dlx, yarn dlx or npm exec.

Register a stdio MCP server named knowledge whose command is knowledge-mcp-connector. Set env KNOWLEDGE_MCP_TOKEN to my access token and env KNOWLEDGE_MCP_URL to the MCP endpoint I give you. Put the token only in the client's MCP settings or config file — never as a CLI flag, never in a URL, and never on a shell command line.

If I have not given you my token or the endpoint, ask me for them and wait. Do not invent a token or use a placeholder. If the client cannot find knowledge-mcp-connector, run knowledge-mcp-connector doctor and use the configuration it prints.

tools/list

read-only knowledge tools — nothing here can change the source

  • dgmcp_resolveA phrase to ranked canonical product, capability and document ids
  • dgmcp_searchRanked whole sections for a question, already filtered to your access
  • dgmcp_get_documentOne approved document with its metadata and source commit
  • dgmcp_list_productsProducts and modules you can read
  • dgmcp_capability_statusSupported, partial, planned, not supported or not documented — with evidence
  • dgmcp_find_integrationsIntegrations, endpoints and their documented limits
  • dgmcp_related_documentsLinked capabilities and integrations you are allowed to see

Your agent only sees the tools your token is scoped for, over the products you can read.

How access works

  1. 01An administrator creates your accountRoles, teams and product access are assigned in the portal. There is no sign-up form.
  2. 02You receive a one-time linkIt works once and expires soon after it is sent. It never contains your token.
  3. 03Set a password, collect your tokenThe token is created when you press the button and shown only on that page.

works with · Claude Code · Claude Desktop · Codex · Cursor · VS Code · Any MCP client

GitLab

single source of truth — the portal never edits knowledge

deny

by default — tokens are scoped by product and tool

audited

every MCP call is logged without document contents