MCP Connector

What This Does

The MCP connector exposes Bombyx memory tools through JSON-RPC.

Use it when your agent, IDE, or local automation already supports Model Context Protocol. Use the REST API when you want normal HTTP endpoints with simpler request shapes.

Before You Start

You need:

A btx_... bearer token
The MCP URL
A connector with the right memory capabilities

Production MCP URL:

https://bombyxlabs.com/app/api/tool-connectors/mcp

Codex Config Example

Store the token in a secret or environment variable named BOMBYX_MCP_TOKEN.

[mcp_servers.bombyx]
url = "https://bombyxlabs.com/app/api/tool-connectors/mcp"
bearer_token_env_var = "BOMBYX_MCP_TOKEN"

Tools

The MCP server exposes these tools:

Tool	What it does
`bombyx_status`	Checks connector identity and capabilities
`bombyx_memory_search`	Searches organization memory
`bombyx_memory_save`	Saves tool-private or organization-internal memory
`bombyx_memory_propose`	Creates a reviewed memory proposal
`bombyx_memory_report_usage`	Reports which recalled memory items were used or ignored

JSON-RPC Example

curl https://bombyxlabs.com/app/api/tool-connectors/mcp \
  -H "Authorization: Bearer btx_your_token_here" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'

Example response:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "tools": [
      {
        "name": "bombyx_status",
        "description": "Check the Bombyx connector identity and capabilities."
      }
    ]
  }
}

Common Mistakes

Putting the raw token in a repo config file.
Calling MCP when a plain REST call would be easier.
Forgetting to restart the client after adding a new MCP server.