Skip to main content
Any MCP-compatible AI client can connect to Tendy’s procurement database using a Personal Access Token (PAT). You generate a token once in your Tendy account settings, then supply it as a Bearer token in your chosen client’s MCP configuration. The steps differ slightly between clients, but the endpoint and authentication scheme stay the same across all of them.

Generate a Personal Access Token

Before configuring any client, create a PAT in Tendy:
  1. In Tendy, go to Settings → Access Tokens.
  2. Click Create token, give it a descriptive name (e.g., mistral-le-chat), and click Generate.
  3. Copy the token immediately — it starts with tndy_pat_ and is shown only once.

Mistral Le Chat

1

Open MCP server settings in Mistral Le Chat

In Mistral Le Chat, navigate to Settings → MCP Servers (or Integrations, depending on your version) and click Add server.
2

Enter the Tendy endpoint and token

Provide the server URL and your PAT. Le Chat accepts a JSON configuration block like this:
Replace tndy_pat_YOUR_TOKEN_HERE with the token you generated in Tendy.
3

Save and test the connection

Save the configuration. Start a new conversation and ask Le Chat to search for tenders — it will call Tendy’s MCP tools automatically.

Grok (xAI)

Grok supports MCP tool integrations through its Integrations or Tools settings panel.
1

Open Grok's integrations settings

In Grok, go to Settings → Integrations (or Settings → Tools) and select the option to add a custom MCP server or external tool.
2

Add the Tendy MCP endpoint

Enter https://tendy.by/api/mcp as the server URL and provide your PAT as the Bearer token in the authorization field. Consult Grok’s MCP documentation for the exact field names and configuration format, as these may change between versions.
3

Save and verify

Save the configuration and start a conversation. Ask Grok to list your saved searches or search for tenders to confirm the connection is working.

Generic MCP Client Configuration

If you are using any other MCP-compatible client or building your own integration, use these connection details: Most clients that follow the standard MCP config file convention accept a block like this:
mcp-config.json
Replace tndy_pat_YOUR_TOKEN_HERE with your actual token. If your client supports OAuth discovery instead of static tokens, point it to https://tendy.by/.well-known/oauth-protected-resource — Tendy’s authorization server will handle the rest.

Tips & Notes

Configuration field names vary between MCP clients. Some use authorization, others use headers.Authorization, and some have a dedicated bearerToken field. Check your client’s documentation for the exact format — the endpoint URL and token value stay the same regardless.
MCP integrations require the Basic plan or above. If you are on the Free plan, upgrade in Settings → Subscription to enable MCP access.
All MCP clients have access to the same set of Tendy tools: search_tenders, get_tender, list_saved_searches, run_saved_search, and list_saved_tenders. For a full description of each tool’s inputs and outputs, see the MCP Tools reference.