Skip to main content

​
Overview

Connectors are pre-built integrations for popular services. This guide covers how to connect them and configure your toolsets.

​
Connect a Service

Most connectors use OAuth for secure, one-click authentication:
1

Click Connect

Find your connector and click the Connect button
2

Authorize Access

You’ll be redirected to the service (e.g., Linear, GitHub, Slack)Review the requested permissions:
  • Read access to issues, projects, etc.
  • Write access to create, update, delete
Click Authorize to grant access
3

Select Workspace/Organization

Some services require you to select a workspace or organization:
  • Linear: Choose workspace
  • Slack: Choose workspace and channel
  • GitHub: Choose organization or personal account
4

Confirmation

You’ll be redirected back to Tadata with a success messageYour account is now connected!
Tadata automatically handles token refresh. Your connection stays active without manual intervention.

​
API Key Connection

Some connectors use API key authentication:
1

Get Your API Key

Find your API key in the service’s settings (usually under Settings → API or Developer)
2

Enter API Key

Paste your API key into the Tadata connection form and configure any additional settings
3

Save

Click Save to complete the connection
Tadata stores all credentials securely in an encrypted manner. You can always revoke access and permanently delete tokens through your dashboard.

​
Select Tools to Enable

After connecting, choose which tools to expose to your AI agents. Enabling all tools is a great way to start. You get maximum flexibility and can discover useful operations you might not have known about. Once your toolset is deployed, you can use AI tool selection in your server settings to automatically suggest the most relevant tools based on your desired use case. This helps your agent focus on the right operations without overwhelming it with options.

​
Create New Toolset vs. Add to Existing

When connecting a connector, choose:

​
Option 1: Create New Toolset

Best for:
  • Your first connector
  • Logically separate use cases (e.g., separate “Support Tools” from “DevOps Tools”)
  • Testing a connector before adding to production toolset
Result: New toolset at {new-name}.mcp.tadata.com

​
Option 2: Add to Existing Toolset

Best for:
  • Combining related services (e.g., Sentry + GitHub + Slack for triage)
  • Building comprehensive workflows
  • Following a Recipe
Result: Tools added to existing toolset URL

Single-Connector Toolset

Linear ToolsConnectors: LinearTools: 5 Linear toolsUse: Simple issue tracking

Multi-Connector Toolset

Triage AgentConnectors: Sentry, GitHub, Slack, RenderTools: 15+ toolsUse: Production incident response

​
Best Practices

​
Security

OAuth is more secure than API keys:
  • Tokens are scoped to specific permissions
  • Tokens can be revoked without changing passwords
  • Tadata handles token refresh automatically
Only enable tools your agent actually needs:
  • Start with read-only tools
  • Add write operations carefully
  • Block destructive tools (delete, archive) by default
Create dedicated service accounts for AI agents:
  • Easier to audit and track actions
  • Can be revoked without affecting human users
  • Clearer permission boundaries
If using API keys (not OAuth):
  • Rotate keys every 90 days
  • Use restricted/scoped keys when possible
  • Monitor key usage in service dashboards

​
Organization

Name toolsets clearly:
  • ✅ “Production Triage Agent”
  • ✅ “Customer Support Tools”
  • ❌ “My Toolset”
  • ❌ “Test 123”
Create different toolsets for:
  • Development (testing, staging APIs)
  • Production (live services)
  • Personal (individual use)
Use Server Groups to organize.

​
Troubleshooting

Symptoms: Redirect fails, “Authorization denied” errorSolutions:
  • Disable popup blockers
  • Try in an incognito/private window
  • Verify you have admin access to the workspace/organization
  • Check that the service is not experiencing an outage
Symptoms: “Invalid API key” or “Unauthorized” errorSolutions:
  • Double-check the API key is copied correctly (no extra spaces)
  • Verify the key has not expired
  • Confirm the key has necessary permissions
  • Check the base URL is correct (for self-hosted services)
Symptoms: “Authentication failed” in PlaygroundSolutions:
  • Check if token has expired (reconnect account)
  • Verify the connected account has access to requested resources
  • Confirm tool permissions are set to “Allow” not “Block”
  • Review error logs in Analytics for specific error messages
Solutions:

​
Next Steps

Test Your Toolset

Use the Playground to test tools interactively

Bring Your Own API

Add custom connectors with OpenAPI specs

Configure Authentication

Deep dive into OAuth and passthrough auth

View Recipes

Pre-configured connector combinations