Agents and MCP

Use the API from Claude Desktop, Cursor and other agents, without writing integration code.

There are two MCP servers, for two jobs. webfold-mcp is the local engine: it runs on your machine and needs no API key (see MCP server). The API MCP server below fronts the hosted API, so an agent can use the hosted endpoints with your key.

API MCP server (stdio)

It speaks MCP 2024-11-05 over stdin and stdout and forwards each tool call to the API with your key.

Tool	Does
`web_scrape`	Scrape a URL to Markdown.
`arxiv_search`, `arxiv_retrieve`	Search arXiv and retrieve a chunked paper.
`youtube_transcript`	Fetch a YouTube transcript.
`bookmark_create`, `bookmark_list`	Archive and search bookmarks.
`collection_create`, `collection_list`	Create and list collections.

Environment variable	Default	Description
`PTYKTOS_API_KEY`	none	Bearer token for the API.
`PTYKTOS_API_URL`	`http://localhost:8080`	Set to `https://api.webfold.ai` for the hosted API.

Claude Desktop or Cursor

{
  "mcpServers": {
    "webfold-api": {
      "command": "/path/to/ptyktos-mcp-server",
      "env": {
        "PTYKTOS_API_KEY": "<your key>",
        "PTYKTOS_API_URL": "https://api.webfold.ai"
      }
    }
  }
}

Code Mode (fixed token footprint)

Instead of one tool per endpoint, the Code Mode server exposes two tools: search(query) returns the available API operations with their parameter schemas, and execute calls any operation. The agent discovers endpoints on demand, so the context cost stays constant as the API grows. A Cloudflare Workers deployment hosts it at the edge for agent access without a local binary.