Takos Context MCP Server

This is an MCP (Model Context Protocol) server that provides context management capabilities.

Usage

Add the following configuration to your MCP client's configuration file:

{
  "mcpServers": {
    "takos": {
      "command": "npx",
      "args": ["@takosai/payments-context@latest"]
    }
  }
}

Setup

Environment Variables

The server requires the following environment variable:

• CONTEXT_API_URL: The URL of the Takos Context API server (defaults to http://127.0.0.1:9000 if not specified)

Development

Building the Project

To build the project, run:

npm run build

This will create a build directory with the compiled JavaScript files.

For Developers (Local Build)

If you're developing or want to use a local build, add the following configuration to your MCP client's configuration file:

{
  "mcpServers": {
    "takos-context": {
      "command": "node",
      "args": ["/ABSOLUTE_PATH/context-mcp/build/index.js"]
    }
  }
}

Replace /ABSOLUTE_PATH/ with the actual absolute path to your context-mcp directory.

Content types

The supported content types in MCP are:

• "text": Plain text content
• "image": Image data with mimeType
• "audio": Audio data with mimeType
• "resource": Resource references

Here's a breakdown of what each means:

✅ text

Plain UTF-8 text meant to be shown as-is to the user.

{ "type": "text", "text": "Hello world" }

🖼️ image

A media object with a MIME type (image/png, image/jpeg, etc.) and a URL or data reference.

{
  "type": "image",
  "mimeType": "image/png",
  "url": "https://example.com/image.png"
}

🔊 audio

Audio data also described by MIME type (audio/mp3, audio/wav, etc.) and a playable source.

{
  "type": "audio",
  "mimeType": "audio/mp3",
  "url": "https://example.com/sound.mp3"
}

📦 resource

Used for generic resources like documents, PDFs, or links to structured data. Usually includes a name, mimeType, and url.

{
  "type": "resource",
  "name": "report.pdf",
  "mimeType": "application/pdf",
  "url": "https://example.com/report.pdf"
}

⸻

🧠 What's Missing (but Supported in Clients like Cursor)

Depending on your implementation or extensions, additional types may also be supported, like: • "code" – for language-tagged code blocks • "markdown" – for rich Markdown rendering • "tool_call" – for invoking tools (special-case internal messages)

But officially, MCP v1 only documents the four types you listed. You can extend these in your server as long as the client (like Cursor) knows how to handle them.

Let me know if you want to add support for custom types like "markdown" or "code" in your MCP server.