MCP
This chapter was written from the product's source code and has not yet been checked by a person on a running Cogneris. If what you see on screen differs, the screen is right — please tell your Cogneris contact so the chapter can be corrected.
The Cogneris MCP server lets an AI assistant in a developer's editor — VS Code, Cursor, Claude Code or any other client of the Model Context Protocol (MCP) — work with your company's Cogneris account: read the API documentation, and create API keys, webhook endpoints and classifiers in plain language. This page gives the server address, ready-made editor configuration, and the developer tokens that keep an editor connected.
| How to get here | Vision menu › MCP. The old Playground chat address now opens this page. |
| Who can use it | Every signed-in member can open the page. Creating, listing and revoking developer tokens is limited to tenant administrators (customer-admin, customer-tech, and Cogneris operators inside their own company), like API keys. What a connected editor may do is set by the token's permissions or, without a token, by your own account. |
| Content status | From source; not observed (vision-fe 0b724a0, mcp-be 863cdb5, billing-be 12ce77c, 2026-10-22) |
The page title is MCP, with the line Connect the Cogneris MCP server to VS Code, Cursor or Claude Code and build with the Cogneris API from your editor: create API keys, webhooks, classifiers, workflows and PDF fill templates.
Server URL
Server URL shows the address editors connect to, with Copy / Copied. The hint says This server is in your account's region. Use the same URL in every editor.
There is one server per data region, for example https://mcp-eu.cogneris.ai/ and https://mcp-us.cogneris.ai/. The page picks the one for your company's region.
Connect your editor
Connect your editor has one tab per editor: VS Code, Cursor, Claude Code. Each tab shows a snippet with the server URL already filled in, and Copy / Copied. The snippets below use the European address as an example.
VS Code
Save this as .vscode/mcp.json in your project. VS Code asks for your developer token the first time and keeps it in its secret storage.
{
"inputs": [
{
"id": "cogneris-token",
"type": "promptString",
"password": true,
"description": "Cogneris developer token"
}
],
"servers": {
"cogneris": {
"type": "http",
"url": "https://mcp-eu.cogneris.ai/",
"headers": { "Authorization": "Bearer ${input:cogneris-token}" }
}
}
}
The tab also has the link Install in VS Code: The one-click install signs you in through the browser instead of asking for a token. (see Signing in without a token).
Cursor
Add this to ~/.cursor/mcp.json and replace the placeholder with your developer token.
{
"mcpServers": {
"cogneris": {
"url": "https://mcp-eu.cogneris.ai/",
"headers": { "Authorization": "Bearer <YOUR_COGNERIS_TOKEN>" }
}
}
}
Claude Code
Run this in your terminal and replace the placeholder with your developer token.
claude mcp add --transport http cogneris\
https://mcp-eu.cogneris.ai/ \
--header "Authorization: Bearer <YOUR_COGNERIS_TOKEN>"
The page shows the same command on one line.
Any other MCP client connects the same way: an HTTP MCP server at the Server URL, with the header Authorization: Bearer followed by the developer token.
Signing in without a token
Prefer to sign in through the browser? — Editors that support OAuth can connect without a token: they open the Cogneris sign-in page and use your account. That session lasts 1 hour, while a developer token keeps you connected for up to 90 days.
When an editor connects without a token, the server answers that sign-in is required and tells the editor where to sign in; an editor that supports OAuth then opens the Cogneris sign-in page. The editor acts with your own account until the session ends, after one hour.
Developer tokens
Developer tokens — A developer token connects your editor to Cogneris on your behalf. It expires on its own, and you can revoke it at any time.
A developer token is a special API key:
- It is tied to the user who creates it; the server records every action under that user.
- It always expires — after 30 or 90 days. The service refuses a developer token without an expiry or with one longer than 90 days.
- It carries the permissions chosen at creation.
- It is created in your company's default production environment, so it starts with
xtkt_live_. - It works only with the MCP server. The MCP server refuses every other API key, and developer tokens do not appear on the API Keys page (see Developers).
Fields
| Field | What it does | Required | Format / values | Default | Validation messages |
|---|---|---|---|---|---|
| Token name | A label, for example the computer it is used on. | Yes | Up to 120 characters. Placeholder Work laptop. | Empty | Generate token stays disabled while empty. |
| Expires in | How long the token works. | Yes | 30 days, 90 days | 90 days | — |
| Permissions | What a connected editor may do. Each option shows its label and its scope. | At least one | See Permissions | Read your resources and Create and change resources | Choose at least one permission. |
Permissions
| Option | Scope | What it allows |
|---|---|---|
| Read your resources | mcp.read | Read tools: who you are, the documentation and API reference, classifiers and their training status, webhook event types, PDF fill templates and fill jobs, downloads of filled PDFs, and your usage summary. |
| Create and change resources | mcp.write | Create and train classifiers and add samples to them; register PDF fill templates, upload source PDFs and start fill jobs. |
| Manage API keys | apikeys.manage | List, create and revoke your company's API keys. Never implied by Create and change resources. |
| Manage webhooks | webhooks.manage | List, create, update, disable, delete and test webhook endpoints, replace their signing secret, and list and replay deliveries. Never implied by Create and change resources. |
A tool whose permission the token lacks is not offered to the editor and refuses to run.
The token list, Active tokens:
| Field | What it shows | Format |
|---|---|---|
| Name | The token name. | Text |
| Token | The last four characters of the token. | •••• and four characters |
| Expires | The expiry date. | Date |
| Last used | Date of the last use, or Never. | Date |
| Actions | Revoke. | — |
Only tokens that are neither revoked nor expired are listed.
Buttons and actions
| Button | What happens | Who | Reversible? |
|---|---|---|---|
| Generate token (Generating… while it runs) | Creates the token and shows it once, with Copy this token now. For your security, it will not be shown again. | Tenant administrators | Revoke the token to undo. |
| Copy / Copied | Copies the new token. | — | — |
| Done | Hides the token. It cannot be shown again. | — | — |
| Revoke | Asks Revoke developer token? — Any editor using "…" loses access within a minute. This cannot be undone. — then Yes, revoke revokes the token; Cancel keeps it. | Tenant administrators | No |
The MCP server reuses a successful token check for up to 60 seconds, so an editor that is already connected can keep working for up to a minute after Revoke.
Common problems
| Message | Cause | What to do |
|---|---|---|
| The token could not be created. Please try again. | The service refused the request — for example your profile is not a tenant administrator. | Ask a tenant administrator to create the token. |
| The token could not be revoked. Please try again. | The revocation failed. | Try again. |
| You have no active developer tokens yet. | No active token — or the list could not be loaded, which the page does not distinguish. | Check your profile with an administrator. |
| The editor keeps asking to sign in | The token expired or was revoked, or the editor signed in through the browser and the one-hour session ended. | Create a new token and update the editor's configuration. |
| Loading tokens… | The list is loading. | — |
What you can ask
What you can ask — Once connected, ask your editor's assistant in plain language. For example:
| Area | Example on the page |
|---|---|
| API keys | Create a sandbox API key for my checkout service. |
| Webhooks | Send every document event to a webhook at https://example.com/hooks. |
| Classifiers | Create a classifier for invoices and receipts, then test it in the Playground with this PDF. |
| Workflows | Build a workflow that extracts the ID card, checks the face match and sends doubtful cases to manual review. |
| Extraction | Extract this invoice with my Invoice classifier and show me the fields as JSON. |
| PDF fill templates | Register a fill template for this PDF form and fill it with the data from my last extraction. |
Limits
| Limit | Value |
|---|---|
| Developer token lifetime | 30 or 90 days, chosen at creation; never more than 90. |
| Browser sign-in session | 1 hour. |
| Revocation delay | Up to 60 seconds for an editor already connected. |
| API keys created from an editor | Sandbox by default. A production key is created only when the request names the production environment and confirms it explicitly. |
| Source PDF upload | 10 MB. |
| Webhook deliveries per page | Up to 25. |
| Documentation read in one call | Up to 6,000 characters; longer pages are read in parts. |
| Request rate | Decided by the service; above it the server answers that the request was rate-limited. |
At this version the server's tools cover API keys, webhooks, classifiers, workflows and their runs, Build AI, PDF fill templates and jobs, usage and documentation. It has no tools for portal forms or Word templates, and the page's examples no longer mention them.
Related
- Developers — API keys and webhook endpoints from the Vision screens.
- Vision administration overview
Last reviewed 2026-10-22 · Version 1.0.0 · Owner: product-documentation