The tool
cortexa_research
Your host agent sees one tool. Cortexa decomposes the research question, searches across 2.1K+ live and curated tools, and returns a cited markdown answer.
Local install with stdio
Most desktop MCP clients use a local subprocess. The zero-install adapter is
npx -y @yoreai/cortexa-mcp.Cursor
Use ~/.cursor/mcp.json for user-wide setup or .cursor/mcp.json inside a workspace.
{
"mcpServers": {
"cortexa": {
"command": "npx",
"args": ["-y", "@yoreai/cortexa-mcp"],
"env": {
"CORTEXA_API_KEY": "sk-cortexa-live-..."
}
}
}
}Claude Desktop
Add the server to Claude's desktop configuration file, then restart Claude.
{
"mcpServers": {
"cortexa": {
"command": "npx",
"args": ["-y", "@yoreai/cortexa-mcp"],
"env": {
"CORTEXA_API_KEY": "sk-cortexa-live-..."
}
}
}
}Codex
Add this TOML block to ~/.codex/config.toml.
[mcp_servers.cortexa]
command = "npx"
args = ["-y", "@yoreai/cortexa-mcp"]
env = { CORTEXA_API_KEY = "sk-cortexa-live-..." }Remote streamable HTTP
HTTP clients do not need a local npm adapter. Point the client at
https://api.cortexa.sh/mcpand pass the same bearer token you use for the API.{
"mcpServers": {
"cortexa": {
"type": "http",
"url": "https://api.cortexa.sh/mcp",
"headers": {
"Authorization": "Bearer sk-cortexa-live-..."
}
}
}
}Smoke test
After you add the config, verify the key, reload the host, and ask one narrow source-backed question.
Confirm the key
Create a named key in Settings so you know which client owns the traffic.
Restart the host
Desktop clients usually need a restart or explicit MCP reload after config changes.
Ask a narrow question
Try: “Use Cortexa to find three cited sources about tau PET endpoints.”