Docs & REST API MCP Server

The Docs MCP Server gives any MCP-compatible AI agent direct access to the Webfuse developer documentation and the REST API. Instead of copy-pasting docs or writing API calls by hand, your agent can search the docs, read specific pages, browse the API schema, and execute REST API calls — all through tool calls.

Use Cases

• AI-assisted development — let your coding agent look up Webfuse APIs, configuration options, and integration guides while it writes code, without leaving the IDE.
• REST API interaction — allow an agent to list API categories, inspect endpoint schemas, and make authenticated API calls on your behalf.
• Support & troubleshooting — build agents that can answer questions about Webfuse by searching the documentation in real time.

Authentication

The Docs MCP Server authenticates with a Company Key (prefixed ck_) from the REST API. Company Keys are scoped to your entire company and grant access to all spaces and API endpoints.

Pass the key in the Authorization header as either a Bearer or Token prefix:

Authorization: Bearer ck_your_company_key

Caution

Documentation tools (search_docs, get_doc_page, list_doc_pages, get_doc_toc) work without authentication. API tools (list_api_categories, list_api_methods, api_call) require a valid Company Key — calls made without one will fail.

Connect your MCP Client

Configure your MCP client to connect to the Docs MCP Server endpoint for your domain:

https://mcp.HOSTNAME/mcp

VS Code

Install in VS Code

Or add manually to .vscode/mcp.json in your workspace, or to user settings:

{
  "servers": {
    "webfuse-docs": {
      "type": "http",
      "url": "https://mcp.HOSTNAME/mcp",
      "headers": {
        "Authorization": "Bearer ${input:company_key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "company_key",
      "description": "Webfuse Company Key",
      "password": true
    }
  ]
}

Cursor

Or add manually to .cursor/mcp.json:

{
  "mcpServers": {
    "webfuse-docs": {
      "type": "http",
      "url": "https://mcp.HOSTNAME/mcp",
      "headers": {
        "Authorization": "Bearer <your-company-key>"
      }
    }
  }
}

Claude

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "webfuse-docs": {
      "type": "http",
      "url": "https://mcp.HOSTNAME/mcp",
      "headers": {
        "Authorization": "Bearer <your-company-key>"
      }
    }
  }
}

Or use the Claude CLI:

claude mcp add-json webfuse-docs '{"type":"http","url":"https://mcp.HOSTNAME/mcp","headers":{"Authorization":"Bearer <your-company-key>"}}'

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "webfuse-docs": {
      "type": "http",
      "url": "https://mcp.HOSTNAME/mcp",
      "headers": {
        "Authorization": "Bearer <your-company-key>"
      }
    }
  }
}

Python SDK

# To install the required library: pip install mcp

import asyncio
import httpx
from mcp import ClientSession
from mcp.client.streamable_http import streamable_http_client

async def main():
    async with streamable_http_client(
        "https://mcp.HOSTNAME/mcp",
        http_client=httpx.AsyncClient(
            headers={"Authorization": "Bearer <your-company-key>"},
            timeout=httpx.Timeout(timeout=None, connect=10.0),
        ),
    ) as (read, write, _):
        async with ClientSession(read, write) as session:
            await session.initialize()

            # Search the documentation
            result = await session.call_tool(
                "search_docs", {"query": "session api"}
            )
            print(result)

            # List API categories
            categories = await session.call_tool("list_api_categories", {})
            print(categories)

if __name__ == "__main__":
    asyncio.run(main())

Testing without an agent

Use the MCP Inspector to explore and call tools interactively:

npx @modelcontextprotocol/inspector

Set Connection Type to Streamable HTTP, enter the MCP server URL, and authenticate with your API key.

Tools

Documentation Tools

These tools are available without authentication.

search_docs

Search the documentation using full-text search.

Parameter	Type	Required	Description
query	string	✓	Search query (supports FTS5 syntax)
limit	number		Maximum number of results to return (default: 10)

get_doc_page

Retrieve a specific documentation page by its URL path.

Parameter	Type	Required	Description
url_path	string	✓	URL path of the page (e.g., "1-introduction" or "3-spaces-&-sessions/01-space-domain")

list_doc_pages

List all available documentation pages. Returns each page’s title and URL path.

No parameters.

get_doc_toc

Get the hierarchical table of contents for the entire documentation.

No parameters.

REST API Tools

These tools require a valid Company Key in the Authorization header.

list_api_categories

List all available API categories (tags) from the OpenAPI schema.

No parameters.

list_api_methods

Get the full endpoint schemas for a given category, with all $ref references resolved.

Parameter	Type	Required	Description
category	string	✓	Category name (tag) to filter by

api_call

Execute an HTTP request against the REST API using an operationId from the OpenAPI schema.

Parameter	Type	Required	Description
operation_id	string	✓	The operationId of the endpoint (e.g., "spaces_list", "spaces_create")
path_params	object		Path parameters to substitute in the URL (e.g., {"space_id": "123"})
query_params	object		Query parameters
body	object		Request body (for POST/PUT/PATCH)

Try it

Connect to the Docs & REST API MCP Server, then ask your agent:

“Search the Webfuse docs for how to configure session recording.”

“List all my Webfuse spaces using the API.”

“Write a Webfuse Extension that adds a floating ‘Back to top’ button on every page.”

The agent will use search_docs and get_doc_page to look up the Extension API, understand the lifecycle hooks and manifest format, and generate a working Extension you can install in your Space — all without you leaving your IDE.