MCP Bone

MCP Bone npm package which is used to connect to MCP Bone as a MCP Server and is also used as SDK

javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "tangshuang-mcp-bone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-bone"
      ],
      "env": {
        "MCP_BONE_ACCESS_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}

MCP Bone MCP Server lets you connect to the MCP Bone service to register MCP servers, obtain tool calling information, and parse tool calls from generated completions. It enables seamless tool discovery and invocation from your MCP client workflow, so you can orchestrate tool usage without writing custom parsers for every response.

How to use

You use the MCP Bone MCP Server by running it in your environment and connecting your MCP client to it. The server exposes tools you can register and reference from your LLM or prompt workflow. When your client generates a completion, you use the server to convert the generated text into a structured set of tool_calls that your downstream logic can execute. This streamlines function calling and keeps tool usage consistent across sessions. You also have an option to parse text outputs into JSON tool representations for cases where the LLM does not natively support tool calls.

How to install

Prerequisites: you need a functioning Node.js environment and access to run commands in your shell.

Set up the MCP Bone token and install the MCP Bone MCP Server integration using NPX. The following configuration demonstrates how to run the MCP Bone server directly with NPX and inject your access token at runtime.

{
  "mcpServers": {
    "mcp_bone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-bone"
      ],
      "env": {
        "MCP_BONE_ACCESS_TOKEN": "YOUR_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Additional setup and usage notes

After starting the server, configure your MCP client to point to the MCP Bone MCP Server using the provided stdio configuration. The token must be valid for MCP Bone access to discover and parse tools.

Security and tokens

Keep the MCP_BONE_ACCESS_TOKEN secret and do not expose it in client-side or public code. Rotate tokens as needed and store tokens securely as environment variables in your deployment environment.

Troubleshooting tips

If tool parsing fails, verify that your token is set correctly in the environment and that the MCP Bone service is reachable. Ensure the token matches the one generated for your App in MCP Bone, and re-run the NPX command if needed.

Available tools

extractAndParseToolsToJson

Parses tool descriptions from text and converts them into a JSON array of tool calls.

extractAndParseToolsXmlToJson

Parses tool descriptions embedded in XML-style text and converts them into a JSON array of tool calls.

extractAndParseToolsTextToJson

Parses plain text tool descriptions into a JSON array of tool calls.