The Deframe MCP Server is hosted and ready to use — no installation required. Point your AI host at the server URL and add your API key to start using all 25 tools and 9 prompts.
Server URL: http://mcp.deframe.io/mcpPrerequisites
A Deframe API key — get one here
An MCP-compatible host: Claude Desktop or similar
Node.js installed (required for npx)
Claude Desktop
Open the configuration file
Open ~/Library/Application Support/Claude/claude_desktop_config.json
Open %APPDATA%\Claude\claude_desktop_config.json
Create the file if it does not exist.
Add the server entry
{ "mcpServers" : { "deframe" : { "command" : "npx" , "args" : [ "-y" , "mcp-remote" , "https://mcp.deframe.io/mcp" , "--header" , "x-api-key:your-api-key" ] } } }
Claude Desktop uses mcp-remote as a bridge to connect to remote HTTP servers. The --allow-http flag is required because mcp-remote enforces HTTPS by default.
Restart Claude Desktop
Close and reopen the app. The Deframe tools will appear in the tool picker. Ask Claude “what Deframe tools are available?” to confirm the connection.
Claude Code
Add the server
claude mcp add --transport http deframe http://mcp.deframe.io/mcp --header "x-api-key:your-api-key"
Edit ~/.claude/mcp.json (global) or .claude/mcp.json (project): { "mcpServers" : { "deframe" : { "type" : "http" , "url" : "http://mcp.deframe.io/mcp" , "headers" : { "x-api-key" : "your-api-key" } } } }
Claude Code supports HTTP transport natively — no mcp-remote required.
Verify the connection
Ask Claude “what Deframe tools are available?” to confirm the connection.
Cursor
Add the server
Create or edit .cursor/mcp.json (project) or ~/.cursor/mcp.json (global): { "mcpServers" : { "deframe" : { "command" : "npx" , "args" : [ "-y" , "mcp-remote" , "http://mcp.deframe.io/mcp" , "--header" , "x-api-key:your-api-key" , "--allow-http" ] } } }
Open Settings (Cmd+Shift+J) → Features → Model Context Protocol
Click Add new MCP server
Fill in Name deframe, Command npx, and the args above
Toggle the server on
The --allow-http flag is required because mcp-remote enforces HTTPS by default.
Verify the connection
Open Cursor and ask in the chat “what Deframe tools are available?” to confirm the connection. The Deframe tools will appear in the tool picker.
Google Gemini CLI
Add the server
gemini mcp add --transport http \ --header "x-api-key:your-api-key" \ deframe http://mcp.deframe.io/mcp
Edit ~/.gemini/settings.json: { "mcpServers" : { "deframe" : { "command" : "npx" , "args" : [ "-y" , "mcp-remote" , "http://mcp.deframe.io/mcp" , "--header" , "x-api-key:your-api-key" , "--allow-http" ] } } }
Verify the connection
Or, inside a Gemini chat session, run /mcp enable deframe. Ask Gemini “what Deframe tools are available?” to confirm the connection.
OpenAI Codex
Add the server
codex mcp add deframe -- npx -y mcp-remote http://mcp.deframe.io/mcp --header x-api-key:your-api-key --allow-http
Edit ~/.codex/config.toml: [ mcp_servers . deframe ] command = "npx" args = [ "-y" , "mcp-remote" , "http://mcp.deframe.io/mcp" , "--header" , "x-api-key:your-api-key" , "--allow-http" ]
Verify the connection
Ask Codex “what Deframe tools are available?” to confirm the connection.
Other Agents Any MCP-compatible host that accepts a mcpServers JSON config can connect to the Deframe server using mcp-remote:
{ "mcpServers" : { "deframe" : { "command" : "npx" , "args" : [ "-y" , "mcp-remote" , "http://mcp.deframe.io/mcp" , "--header" , "x-api-key:your-api-key" , "--allow-http" ] } } }
Replace your-api-key with your Deframe API key. The --allow-http flag is required because mcp-remote enforces HTTPS by default.
Next Steps
Tools Reference Browse all 25 tools and 9 prompts with inputs and outputs
MCP Server Overview Learn what the server does and when to use it
