Skip to main content
Connecting an AI assistant to Tendy takes two steps: obtaining credentials and adding the Tendy MCP server to your client’s configuration. Tendy supports two authentication paths — a Personal Access Token (PAT) for clients that require manual setup, and OAuth 2.1 for Claude and ChatGPT verified connectors that handle authorization automatically.

​
Step 1: Generate a Personal Access Token

If you are using OAuth 2.1 with Claude or ChatGPT, you can skip this step — those clients will prompt you to authorize via browser instead.
1

Open Access Tokens

Sign in to Tendy and navigate to Settings → Access Tokens.
2

Create a new token

Click New token.
3

Name your token

Enter a descriptive name so you can identify where the token is used later — for example, Claude connector or ChatGPT desktop.
4

Copy the token

Tendy displays your new token once. Copy it now and store it somewhere safe — you will not be able to view it again. The token begins with tndy_pat_.
Your PAT grants access to your Tendy account data, including saved searches and bookmarked tenders. Store it in a password manager or secrets vault. If the token is ever exposed, revoke it immediately from Settings → Access Tokens.

​
Using OAuth 2.1 (for Claude and ChatGPT)

Claude Desktop and ChatGPT support OAuth 2.1 natively. When you add the Tendy MCP server to either client, they automatically fetch the Tendy authorization server metadata from the OAuth discovery document and redirect you to a Tendy sign-in page to grant access. No token copying or header configuration is required. OAuth discovery document: https://tendy.by/.well-known/oauth-protected-resource Follow your client’s own documentation to add a new MCP server by URL, then complete the in-browser authorization prompt when it appears.

​
Configuring a PAT-based MCP client

For clients that require manual configuration, add the Tendy server to your MCP config file using your PAT as a Bearer token. The structure below follows the convention used by most MCP-compatible clients — replace tndy_pat_YOUR_TOKEN_HERE with the token you copied in Step 1.
mcp-client-config.json
The exact location and format of the MCP configuration file varies by client. Consult your client’s documentation for where to place this block.

​
Revoking a token

If you no longer need a token or suspect it has been compromised, revoke it immediately:
  1. Go to Settings → Access Tokens.
  2. Click the token you want to remove.
  3. Click Revoke.
Revoking a token disconnects any MCP client that was using it. OAuth sessions can be revoked separately from Settings → Connected Apps.