AI Assistants & MCP

View page Markdown AI documentation index

On this page

Connect Claude, Cursor, VS Code, Codex or any MCP client to the TNID documentation, and let your app ask the docs a question from inside the API.

TNID's documentation is available to AI coding assistants through the Model Context Protocol (MCP), an open standard that lets an assistant call outside tools. Connect the server below and your assistant can search these docs and read any page instead of guessing from stale training data.

The documentation MCP server

Setting	Value
Server URL	`https://support.tsgglobal.com/docs/tnid/mcp/`
Transport	Streamable HTTP
Authentication	None. The server only reads public documentation.
Cost	Free

The server covers both the guides and the API Reference section of this site. It exposes two read-only tools:

Tool	What it does
`searchDocumentation`	Full-text search across every page. Returns matching titles, summaries and links.
`getPage`	Fetches the complete Markdown of one page by its URL, for example `https://support.tsgglobal.com/docs/tnid/company/search-companies.md`.

This server covers documentation only. It cannot log in, create connections, send subscription requests or call the TNID API. Your tokens and client secrets never pass through it. To act on the platform, your code still calls the /user and /company GraphQL servers described in this documentation.

Connect your assistant

Claude Code

Run once in your terminal:

claude mcp add --transport http tnid-docs https://support.tsgglobal.com/docs/tnid/mcp/

Then ask, for example, "Using the TNID docs, write a client that authenticates as a company and lists pending B2B connection requests."

Claude.ai / Desktop

Open Settings → Connectors → Add custom connector, name it "TNID docs", and paste https://support.tsgglobal.com/docs/tnid/mcp/ as the URL. No authentication is needed. Enable it in a chat from the tools menu.

Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

{
  "mcpServers": {
    "tnid-docs": {
      "url": "https://support.tsgglobal.com/docs/tnid/mcp/"
    }
  }
}

VS Code

Add to .vscode/mcp.json in your workspace, then start the server from the MCP view:

{
  "servers": {
    "tnid-docs": {
      "type": "http",
      "url": "https://support.tsgglobal.com/docs/tnid/mcp/"
    }
  }
}

Codex

codex mcp add tnid-docs --url https://support.tsgglobal.com/docs/tnid/mcp/

Other clients

Any MCP client that supports streamable HTTP can connect. Point it at https://support.tsgglobal.com/docs/tnid/mcp/ with no bearer token. stdio and SSE transports are not offered.

Other machine-readable formats

Resource	URL	Use it for
Index of all pages with summaries	`https://support.tsgglobal.com/docs/tnid/llms.txt`	Give an assistant a map of the docs
Every page in one file	`https://support.tsgglobal.com/docs/tnid/llms-full.txt`	Load the whole guide into context
Any single page	Append `.md` to its URL, e.g. `https://support.tsgglobal.com/docs/tnid/getting-started-guide.md`	Fetch one page without HTML
API Reference	docs.tnid.com/api-reference (every page also available with `.md`)	Every query, mutation, type and enum, generated from the API source
One-page API summary	API Quick Reference	Environments, authentication, feature map, webhooks and pagination in a single read

Ask the docs from inside the API

Both GraphQL servers expose a mutation that answers a natural-language question from this documentation and names the pages it drew on. It is useful for in-app help and for agents that already hold a TNID token:

mutation ($question: String!) {
  askDocsQuestion(question: $question) {
    answer
  }
}

A user token is answered from the user half of the reference, a company token from the company half. See the API Reference: user assistant, company assistant.

What to expect

Answers are grounded in the published documentation. If a page is wrong, the assistant will be wrong too. Report documentation issues to support@tsgglobal.com.
The assistant still needs your credentials to run code against the API. Keep client secrets and tokens in environment variables, never in prompts or chat history.
Prompts that work well: "Search the TNID docs for how B2C subscription requests are accepted and write the webhook handler", "Which server, /user or /company, exposes createSpamReport?", "Compare the plain and paginated variants of b2bConnections."

Questions or ideas for the MCP server? Email support@tsgglobal.com.