Keywords AI MCP server: 67 tools, renamed Respan
The product changed name, and the connector is large. What its ten tool groups cover, and the header that registers only the tools you name.
Checked 6 October 2026 · from The vendor's own MCP documentation and its open-source server, published under the Respan name
One of 91 guides to monitoring and developer tools. Each covers what an AI coding agent can get out of the tool through MCP, the protocol that lets the agent query the tool directly.
Summary
Keywords AI now trades as Respan, and its MCP server is documented under that name at mcp.respan.ai/mcp. Its open-source server, respanai/respan-mcp, registers 67 tools across ten groups.
The groups are the shape of a language-model observability platform: logs, traces, customers, prompts, experiments, evaluators, datasets, evaluation pipelines, workflows and organizations.
It is one of the few connectors here with documented ways to register less. A Respan-Enabled-Tools header takes a comma-separated list of exact tool names. Omitting the header makes all 67 tools available. An API key with Write unchecked keeps the agent to reads.
What is the Keywords AI MCP server?
It is Respan's server for the Model Context Protocol. The product traces language-model calls and evaluates them, so a connected agent reaches both the traffic and the scoring.
The reading surface is the useful half for most sessions. list_logs and get_log_detail cover request history, while list_traces and get_trace_tree cover structure and get_spans_summary aggregates spans.
The authoring half covers prompt versions, evaluators and workflows, which most observability connectors do not expose. Prompts have versions that can be created and deployed, and evaluators and workflows have their own commit tools.
It is strongest in agent observability, touches cost through logged usage, and reaches nothing in code review or CI.
| Part of the work | What Keywords AI has here | Can an agent reach it |
|---|---|---|
| Code, tests & review | None | Nothing for code or review |
| CI & release | Prompt and workflow deployment | Partial. Deploying a prompt version or a workflow is a release action, but no pipeline is reachable |
| Production observability | Logs and traces of model calls | Partial, and only for model traffic. There are no service metrics and no request traces |
| Agent observability & evals | Logs, traces, experiments, evaluators, pipelines, datasets | Yes. Core strength, across ten tool groups |
| AI cost management | Usage recorded on logs | Partial. Cost and token usage appear where the platform recorded them on a log; there is no billing surface |
For an agent, that means Respan answers what your model calls did, what they scored and what they cost. It can also deploy the next prompt version. It sees nothing outside model traffic, so a service question needs a separate connector.
What can an AI agent do with Keywords AI?
| Task | Tools | Works | Watch out for |
|---|---|---|---|
| Read recent model calls | Enable Logs list_logs get_log_detail | Yes | Both tools read |
| Follow a trace | Enable Traces list_traces get_trace_tree get_spans_summary | Yes | The tree is the structural view; summaries aggregate |
| Find a customer's traffic | Enable Customers list_customers get_customer_detail | Yes | Customer here means an end user of your product, not an account of yours |
| Manage prompt versions | Enable Prompts list_prompts get_prompt_detail create_prompt_version deploy_prompt_version | Yes | deploy_prompt_version changes what production serves |
| Run and read an experiment | Enable Experiments list_experiments get_experiment create_experiment | Yes | Creating an experiment writes, and delete_experiment removes one |
| Author an evaluator | Enable Evaluators create_evaluator commit_evaluator delete_evaluator | Yes | Commit and delete both change scoring configuration |
| Work with datasets | Enable Datasets create_dataset bulk_create_dataset_logs delete_dataset | Yes | Bulk creation adds many rows in one call |
Decide the tool scope before the first session. With 67 tools registered by default, the Respan-Enabled-Tools header is the difference between a focused connection and a large one.
67 tools registered across ten groups, all on unless a header narrows them. 33 read, and 34 write, run or deploy
- Logs3
list_logsget_log_detailget_spans_summary- Traces2
list_tracesget_trace_tree- Customers2
list_customersget_customer_detail- Prompts4
list_promptsget_prompt_detaillist_prompt_versionsget_prompt_version_detail- Prompts, write5
create_promptupdate_promptcreate_prompt_versionupdate_prompt_versiondeploy_prompt_version- Experiments5
list_experimentsget_experimentlist_experiment_spansget_experiment_spanget_experiment_score_averages- Experiments, write2
create_experimentdelete_experiment- Evaluators3
list_evaluatorsget_evaluatorlist_evaluator_versions- Evaluators, write6
create_evaluatortest_evaluatorcommit_evaluatorupdate_evaluatordelete_evaluatorrun_evaluator- Datasets6
list_datasetsget_datasetlist_dataset_logsretrieve_dataset_logsummarize_dataset_logslist_dataset_eval_runs- Datasets, write7
create_datasetupdate_datasetimport_dataset_logsdelete_datasetreplace_dataset_logremove_dataset_logsbulk_create_dataset_logs- Evaluation pipelines2
list_evaluation_pipelinesget_evaluation_pipeline- Evaluation pipelines, write2
create_evaluation_pipelineupdate_evaluation_pipeline- Workflows5
list_workflowsfilter_workflowsget_workflowlist_workflow_versionsget_workflow_version- Workflows, write11
create_automation_workflowcreate_monitor_workflowcreate_export_workflowcreate_workflowcreate_workflow_draftupdate_workflowdelete_workflowcommit_workflowdeploy_workflowundeploy_workflowvalidate_workflow- Organizations, OAuth only1
list_organizations- Organizations, write1
switch_organization
Groups follow the server's own registration modules in respanai/respan-mcp, read 6 October 2026. The write marks come from each tool's name and description. validate_workflow sends real preview notifications and webhooks, so it is marked as a write.
What the tool definitions cost in context
A client that loads every tool definition at the start of a session spends this much context before the first question. Claude Code defers definitions by default through tool search, and loads a tool's definition when the agent needs it. The method below gives the version and date measured.
A context window is the amount of text a model can hold at once. On 24 August 2026, the 55 documented tools cost 2,815 to 3,407 tokens on Claude with the whole surface loaded. Each description was one short line. The server now registers 67 tools, so a full session today costs more.
The Respan-Enabled-Tools header narrows the set to named tools, so a scoped session pays less. The 24 August figure is also a floor, because it counts names and descriptions only.
| Tool set | Tools | Tokens (GPT-5.6, GPT-5.5) | Tokens (GPT-4, GPT-3.5) | Tokens (Claude Haiku 4.5 to Opus 5) | Share of a 200,000-token window |
|---|---|---|---|---|---|
| Every tool documented on 24 August 2026 | 55 | 847 to 1,390 | 832 to 1,375 | 2,815 to 3,407 | 0.4% to 1.7% |
Encodings: GPT-5.6, GPT-5.5 o200k_base; GPT-4, GPT-3.5 cl100k_base; Claude Haiku 4.5 to Opus 5 count_tokens. Counted from the 55 tool entries in the vendor's own documentation on 24 August 2026.
The hosted server returned 401 to an unauthenticated tools/list, so no input schemas were counted. These figures cover each tool's name and description only. They are a floor.
The Claude columns are measured through the API's count_tokens endpoint, with an empty schema per tool. So they cover the same content as the GPT columns. The range there is two tokenizer generations. Haiku 4.5 and Opus 4.6 sit at the low end. Opus 5 and Sonnet 5 sit at the high end. The gap between them is about a fifth.
Can Keywords AI watch your own AI agents?
It is the most complete agent-observability surface measured across these vendor guides, with only cost left partial. Read from the server source on 6 October 2026.
| Signal | Covered | Notes |
|---|---|---|
| Trace and session tracking | Yes | list_traces, get_trace_tree and get_spans_summary |
| Eval scores on recorded traffic | Yes | Nine evaluator tools, including run_evaluator on a single log, plus get_experiment_score_averages |
| Prompt version tracking | Yes | list_prompt_versions, get_prompt_version_detail, create_prompt_version and deploy_prompt_version |
| Offline experiments | Yes | Experiments and datasets both have their own tools, with list_dataset_eval_runs joining them |
| Token and cost tracking | Partial | Usage is recorded on logs and read through them. There is no dedicated cost tool |
Keywords AI MCP server limits: where answers come back incomplete
Keywords AI starts with a large default surface and a changed brand; those two facts shape the limits below.
The product is documented as Respan, not Keywords AI.
The MCP documentation, the endpoint hostname and the scoping header all use the Respan name. Searching under the original brand finds the company rather than the connector.
Guard: Search and configure under Respan, and keep the old name only as a way to recognize the product.
The agent says: “There are a lot of tools here.” All 67 register unless you narrow them.
The server registers every tool unless a Respan-Enabled-Tools header lists exact tool names. The filter runs in the server's request handler.
Guard: Write the enabled list once per kind of session, and treat the full 67 as the exception rather than the default.
The agent says: “I have updated the prompt.” Deployment is a separate, live step.
create_prompt_version and update_prompt_version change a version, while deploy_prompt_version is what makes it serve.
Guard: Exclude deploy_prompt_version from the enabled list unless deploying is the point of the session.
How to configure Keywords AI MCP for agents
- 1
Whitelist the tools you need
Respan-Enabled-Toolstakes a comma-separated list of exact tool names; without it, all 67 are available. - 2
Uncheck Write for a read-only session
An API key carries Read, Write and Gateway permissions, and a key without Write keeps the agent to reads.
- 3
Pick the credential by scope
An API key reaches only the project it was created in. OAuth acts as you in your active organization, and the organization tools need it.
- 4
Decide who may deploy
deploy_prompt_versionchanges what production serves, anddeploy_workflowmakes a committed workflow version live. - 5
Know the name
Everything is published as Respan, so searching for Keywords AI documentation will send you in circles.
Paste this into your agent’s instructions
Deployment tools sit in the same list as reading tools, and the tool scope can differ per connection. Both belong in the answer.
When you answer using Respan MCP tools, state: - The project and period the answer covers. - Whether the session was scoped with Respan-Enabled-Tools, and which tools were enabled. - Whether you deployed anything. deploy_prompt_version changes what production serves. Never state that data does not exist. State that no logs or traces matched the filters above. Write your answer in ASD-STE100 Simplified Technical English. Use short sentences with one idea in each.
Do you need the MCP server at all?
Not for a scheduled export. Respan has a REST API, and for that job it avoids both the context cost and the write surface.
The connector earns its place when the loop is short: read the failing trace, adjust the prompt version, and evaluate it without leaving the editor.
For tracing alone, Langfuse and Arize Phoenix cover that ground with narrower connectors.
Connect a scoped session for prompt and evaluation work. Use the API for reporting.
Keywords AI MCP server setup
The server is hosted, so nothing is installed. The documentation starts with an API key, passed as a bearer token. Uncheck Write on the key for a read-only connection.
OAuth sign-in works without a key and acts as you in your active organization.
Respan Enterprise uses https://mcp.respan.ai/mcp/enterprise in place of the platform URL. A separate docs server at https://mcp.respan.ai/mcp/docs has one tool, search_docs, and needs no key.
Claude Code
The API key travels as a bearer token. Leave the header out to sign in with OAuth instead.
claude mcp add --transport http respan \ https://mcp.respan.ai/mcp \ --header "Authorization: Bearer <your-respan-api-key>"
Cursor
In ~/.cursor/mcp.json. The same API key applies.
{"mcpServers":{"respan":{
"url":"https://mcp.respan.ai/mcp",
"headers":{"Authorization":"Bearer <your-respan-api-key>"}}}}Codex CLI
Codex reads TOML, so the JSON blocks above will not transfer. The key still applies.
[mcp_servers.respan]
url = "https://mcp.respan.ai/mcp"
headers = { Authorization = "Bearer <your-respan-api-key>" }Every other client
Each block below is the configuration for one client, with the file path and the key that client expects.
Claude Desktop
macOS ~/Library/Application Support/Claude/claude_desktop_config.json. Windows %APPDATA%\Claude\claude_desktop_config.json. There is no CLI. Edit through Settings, Developer, Edit Config.
Quit and restart fully for changes to load. Paths in args must be absolute. Logs at ~/Library/Logs/Claude/mcp.log.
{"mcpServers":{"respan":{"url":"https://mcp.respan.ai/mcp",
"headers":{"Authorization":"Bearer <your-respan-api-key>"}}}}Gemini CLI
~/.gemini/settings.json globally, or .gemini/settings.json per project. Key mcpServers. CLI: gemini mcp add.
{"mcpServers":{"respan":{"url":"https://mcp.respan.ai/mcp",
"headers":{"Authorization":"Bearer <your-respan-api-key>"}}}}VS Code Copilot
.vscode/mcp.json per workspace, or your user profile. CLI: code --add-mcp.
{"servers":{"respan":{"url":"https://mcp.respan.ai/mcp",
"headers":{"Authorization":"Bearer <your-respan-api-key>"}}}}`.vscode/mcp.json` takes the key `servers`. VS Code also reads mcpServers from a portable .mcp.json at the project root or ~/.copilot/mcp-config.json. Its docs recommend the portable files for new servers.
Windsurf
~/.codeium/windsurf/mcp_config.json, which is the path Windsurf documents. Key mcpServers, the same JSON shape as Cursor, carrying the same credential.
Zed
~/.config/zed/settings.json, carrying the same credential as the blocks above.
The key is `context_servers`. Zed does not call them MCP servers in config, so searching its settings for mcp finds nothing.
Google Antigravity
~/.gemini/config/mcp_config.json globally, or .agents/mcp_config.json per project. Key mcpServers. There is no CLI. Use the /mcp overlay in the editor. Supports stdio, streamable HTTP, SSE and websocket.
{"mcpServers":{"respan":{"url":"https://mcp.respan.ai/mcp",
"headers":{"Authorization":"Bearer <your-respan-api-key>"}}}}Amp (Sourcegraph)
~/.config/amp/settings.json or .amp/settings.json, carrying the same credential. The amp mcp CLI covers approve, doctor and oauth.
The key is `amp.mcpServers`, namespaced. A bare mcpServers block is ignored.
Cline
~/.cline/mcp.json per the docs. The source also reads ~/.cline/data/settings/cline_mcp_settings.json. Key mcpServers, standard JSON shape, carrying the same credential. Supports stdio, streamable HTTP and SSE.
Goose (Block)
~/.config/goose/config.yaml, carrying the same credential.
YAML, and servers are called `extensions`. Goose does not use the MCP vocabulary in config at all. Add one interactively with goose configure, or per session with goose session --with-extension.
Kiro (AWS)
.kiro/settings/mcp.json per workspace, or ~/.kiro/settings/mcp.json globally. Key mcpServers, standard JSON shape, carrying the same credential.
Warp
~/.warp/.mcp.json or .warp/.mcp.json. Key mcpServers, standard shape, carrying the same credential. Also addable through the /agent-add-mcp skill.
JetBrains Junie
.junie/mcp/mcp.json per project, or ~/.junie/mcp/mcp.json. Key mcpServers, carrying the same credential. Use /mcp in the CLI to manage.
Roo Code
.roo/mcp.json per project. The global file is mcp_settings.json, opened from the Roo Code MCP settings view with Edit Global MCP. Key mcpServers, carrying the same credential.
Continue
.continue/mcpServers/*.yaml, one file per server, carrying the same credential.
YAML, and `mcpServers` is a list, not an object. Every JSON client keys servers by name. Continue takes an array, so a converted config will not parse.
Trae
.trae/mcp.json per project, or paste into the UI under Raw Config (JSON). Key mcpServers, standard shape, carrying the same credential.
Devin
Devin has no config file to edit. Servers are added through a web form in the settings UI, and Devin's documentation states you do not need to write or paste JSON. The block below is the shape those fields describe, shown for reference. Either route uses the same credential.
Registering only some tools
The documented way to shrink the surface. The API key is unchanged; the extra header lists the exact tool names to enable.
claude mcp add --transport http respan \ https://mcp.respan.ai/mcp \ --header "Authorization: Bearer <your-respan-api-key>" \ --header "Respan-Enabled-Tools: list_logs,get_log_detail"
Read-only access, permissions and security
Prompts, prompt versions, evaluators, pipelines, workflows and datasets can all be created or changed
34 of the 67 tools write, run or deploy.
Three tools change what runs live
deploy_prompt_versionchanges what production serves, anddeploy_workflowandundeploy_workflowstart or stop a workflow.Deletion is reachable
delete_evaluator,delete_dataset,delete_experimentanddelete_workflowall register by default.remove_dataset_logscan wipe a dataset's contents.A read-only key is available
An API key with Write unchecked keeps the agent to reads, whatever the enabled-tools header says.
Traces carry prompt content
A trace tree includes the model calls it describes, so that content reaches the model reading it.
Troubleshooting
- The endpoint returns 401
- An unauthenticated request is rejected with an Unauthorized error. Pass the API key as a bearer token, or complete OAuth.
- Documentation cannot be found under Keywords AI
- The product is published as Respan. The MCP documentation lives under the Respan domain rather than the original brand.
- All 67 tools appear in the client
- All 67 tools register unless narrowed. Add the
Respan-Enabled-Toolsheader with the exact tool names you want. - Production behavior changed after a session
- Check for a deployment.
deploy_prompt_versionis in the default tool list.
Keywords AI MCP server: Reference
| Item | Value |
|---|---|
| Endpoint | mcp.respan.ai/mcp |
| Enterprise endpoint | mcp.respan.ai/mcp/enterprise |
| Docs server | mcp.respan.ai/mcp/docs, one tool (search_docs), no key |
| Brand | Keywords AI now trades as Respan; docs are published under that name |
| Auth | API key as a bearer token, or OAuth sign-in. The organization tools need OAuth |
| Tools | 67 registered across 10 groups, as of 6 October 2026 |
| Scoping | Respan-Enabled-Tools header, comma-separated exact names |
| Read-only | Uncheck Write on the API key |
| Deploying tools | deploy_prompt_version, deploy_workflow |
| Inventory source | The open-source server respanai/respan-mcp, read 6 October 2026 |
What engineers report
The server source is public, so the counts below come from its own registration calls.
| What was checked | What it shows |
|---|---|
| Registered tools | 67 |
| Tool groups | 10 |
| Authentication routes | 2: API key and OAuth |
| Endpoints documented | 3: platform, enterprise and docs |
| Scoping mechanism | Respan-Enabled-Tools header, or a key without Write |
| Deploying tools | 2, plus undeploy_workflow |
Tool inventory read from respanai/respan-mcp on 6 October 2026. Authentication routes, endpoints and the scoping header read from the vendor's MCP documentation, published under the Respan name, the same day. An unauthenticated tools/list against mcp.respan.ai/mcp returned 401 on 6 October 2026.
Should you connect an agent to Keywords AI?
Yes. Best for a scoped enabled-tools list per session, with deploy_prompt_version left out unless deploying is intended.
- Strongest fit
- Teams already tracing model calls with this platform who want prompt and evaluation work inside the editor.
- Main advantage
- A documented header for registering only the tools a session needs, plus a read-only API key, which few connectors here provide.
- Main weakness
- The rename means most existing references point at a brand the documentation no longer uses.
- Operational risk
- Deployment and deletion tools register by default alongside the reading ones.
From Oodle
One platform for agent traces and infrastructure
Agent traces usually sit in a different product from the rest of your telemetry, so when a slow database makes an agent slow the symptom is in one tool and the cause is in another. Oodle keeps both in one query surface.
See agent observabilityFrequently asked questions
How many tools does the Keywords AI MCP server have?
67 registered across ten groups, counted from the open-source server respanai/respan-mcp on 6 October 2026.
Why does the documentation say Respan?
Keywords AI now trades as Respan. The endpoint, the documentation and the scoping header all use that name.
Can I register fewer tools?
Yes. The Respan-Enabled-Tools header takes a comma-separated list of exact tool names. Leaving it out registers all 67 tools. An API key with Write unchecked keeps the agent to reads.
How does authentication work?
An API key as a bearer token, or OAuth sign-in in the browser. An API key reaches one project. OAuth acts as you and is needed for the organization tools.
Can an agent change production?
Yes. deploy_prompt_version changes what production serves, deploy_workflow makes a workflow live, and several delete tools are in the default list.