Skip to main content
The MCP Inspector is an official debugging tool for testing MCP servers. Use it to verify your Autype MCP connection, explore available tools, and test tool calls interactively.

​
Installation

Install the MCP Inspector globally via npm: 
npm install -g @modelcontextprotocol/inspector
Or use npx to run it without installing: 
npx @modelcontextprotocol/inspector

​
Connecting to Autype MCP

The Inspector runs outside of Docker and connects to the MCP server via HTTP.

​
Using the hosted server

mcp-inspector \
  --transport http \
  --url https://mcp.autype.com/mcp/ \
  --header "X-API-Key: YOUR_API_KEY"
Replace YOUR_API_KEY with your actual API key from the Dashboard.

​
Using a self-hosted server

If you’re running the MCP server locally (e.g., via Docker on localhost:8000): 
mcp-inspector \
  --transport http \
  --url http://localhost:8000/mcp/ \
  --header "X-API-Key: YOUR_API_KEY"
The Inspector connects to the MCP server from outside Docker, so use localhost (not autype-mcp or container names).

​
Using the Inspector

Once connected, the Inspector opens a web interface (usually at http://localhost:5173) where you can:
  1. View available tools — See all 17 Autype tools with their parameters and descriptions
  2. Read resources — Inspect the document schema resources (autype://schemas/document, etc.)
  3. Test tool calls — Call tools interactively and see the responses
  4. Debug errors — View detailed error messages and request/response logs

​
Example workflow

  1. List tools — Verify all Autype tools are available
  2. Read schema — Open autype://schemas/document to see the full document structure
  3. Test render — Call render_markdown with sample content: 
    {
  "content": "# Test Document\n\nThis is a test.",
  "document_type": "pdf"
}
  4. Check response — Verify you receive a downloadUrl in the response

​
Troubleshooting

​
Connection refused

If you see “Connection refused” when connecting to localhost:8000:
  • Verify the MCP server is running: docker ps | grep autype-mcp
  • Check the port mapping: docker port autype-mcp
  • Ensure you’re using localhost, not 127.0.0.1 or 0.0.0.0

​
401 Unauthorized

If you see “401 Unauthorized”:
  • Verify your API key is correct
  • Check the header format: --header "X-API-Key: YOUR_API_KEY" (with quotes)
  • Ensure the API key is active in the Dashboard

​
Tools not showing up

If no tools appear in the Inspector:
  • Check the MCP server logs: docker logs autype-mcp
  • Verify the server is healthy: curl http://localhost:8000/health
  • Try reconnecting with the Inspector

​
Advanced: Custom server URL

If your self-hosted MCP server is behind a reverse proxy or uses a custom domain: 
mcp-inspector \
  --transport http \
  --url https://mcp.your-domain.com/mcp/ \
  --header "X-API-Key: YOUR_API_KEY"

​
Next steps

Once you’ve verified the connection with the Inspector, you can connect your AI agent or IDE using the same URL and API key.

Claude Desktop

Connect to Claude Desktop app

Cursor

Connect to Cursor IDE

Windsurf

Connect to Windsurf IDE

VS Code

Connect to VS Code with Copilot