Skip to main content
Cursor connects to remote MCP servers with custom headers, configured in an mcp.json file.

Before you start

  • A Quotable API key from Settings → API keys. See Authentication.
  • The key in an environment variable that Cursor can see, for example in your shell profile:
    Start Cursor from a shell where the variable is set, or set it at the operating-system level.

Add the server

Choose where the configuration lives: Add a quotable entry under mcpServers:
mcp.json
Cursor replaces ${env:QUOTABLE_API_KEY} with the variable’s value when it connects.
If you paste the key directly into headers instead, keep the file out of version control.

Check the connection

Open Cursor’s settings and find Quotable in the MCP server list. It should be enabled with its tools, such as list_projects, get_visibility and list_citations. See Tools for the full list. If it shows an error, open the Output panel and pick MCP Logs from the dropdown. A 401 means the Authorization header is missing or the key is wrong. If QUOTABLE_API_KEY isn’t set in Cursor’s environment, the header carries no key. See Troubleshooting.

Try it

In Agent chat, ask:
Cursor asks for approval before it runs MCP tools, unless you’ve allowlisted them. Every Quotable tool reads data except run_agent, which starts an agent run and uses your workspace’s credits, so leave it off your allowlist.

Next steps

Example prompts

Ready-to-use questions for your workspace.

Workflows

Turn Quotable data into content briefs in your repo.

Tools reference

Inputs and outputs for each tool.
Last modified on November 18, 2026