Charliehub · by A.N.D.Why

Building block 10 · Going further

Sharing outward

One line on a tool lets other AI apps on the same computer use it, starting with Claude Code. They run your tool through Charlie, with the same settings, data and file access a Charlie conversation gets.

What you'd use it for

In your manifest

From the sqlite extension. All three of its tools are shared this way, and so are the three tools in hub-database.

sqlite / manifest.json (trimmed)
{
  "name": "sqlite",
  "tools": [
    {
      "name": "query",
      "description": "Run SQL against the local SQLite database...",
      "handler": "./handlers/query.js",
      "mcp": true
    },
    {
      "name": "describe",
      "description": "Look at the database's structure...",
      "handler": "./handlers/describe.js",
      "mcp": true
    }
  ]
}

What each part means

FieldWhat it does
mcpSet on a tool. true also offers the tool through Charlie's MCP server. Off unless you set it.

Turning it on

  1. Mark the tool

    Add "mcp": true to the tool, then restart Charlie so it reads the change.

  2. Switch on the server

    In Charlie, open Settings > Tool use and tick Serve extension tools over MCP. This takes effect straight away. It is off until you turn it on.

  3. Register Charlie once

    The same section shows a claude mcp add command. Copy it and run it in a terminal. Claude Code then lists your tools under the server name charlie, with the same names Charlie uses, such as sqlite__query.

Things to know

See it in

None of the five examples on this site shares its tools. Two installed extensions do: sqlite and hub-database.

Every field in detail: mcp in the reference.