Developer MCP Integration

1. Scoped Personal Access Tokens (PATs)

All MCP interactions require a cryptographically generated Personal Access Token prefixed with bdt_. Always grant the minimum necessary scopes:

2. Testing Connection via CLI

Before wiring up an agent, verify that your token is valid and can communicate with the BotDigit Gateway:

# Test connection using npx
BOTDIGIT_API_TOKEN="bdt_your_token_here" npx -y @botdigit/mcp-server --test-connection

3. Calling Tools via TypeScript SDK

Use the official @modelcontextprotocol/sdk to integrate BotDigit MCP directly into custom Node.js/TypeScript applications:

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";

const transport = new StdioClientTransport({
  command: "npx",
  args: ["-y", "@botdigit/mcp-server"],
  env: {
    BOTDIGIT_API_TOKEN: process.env.BOTDIGIT_API_TOKEN!,
  },
});

const client = new Client(
  { name: "custom-agent-worker", version: "1.0.0" },
  { capabilities: {} }
);

await client.connect(transport);

// Call BotDigit MCP Tools
const result = await client.callTool({
  name: "search_freelancers",
  arguments: { query: "Rust PostgreSQL backend", limit: 5 }
});

console.log(result.content[0].text);