Connect AI clients to Barndoor - Barndoor Documentation
Overview
Add your Barndoor ToolIQ endpoint found here to your favorite chat client. If you’re not already logged in, you’ll be redirected to Barndoor to authenticate and authorize the MCP servers you want to access.
If you ever want to see what servers you’re connected to, click here.
Connect Your Chat Client
Select your preferred AI chat client below to see detailed connection instructions:
Claude
Prerequisites:
- Active Claude account (Pro, Max, Team, or Enterprise plan)
- Universal Barndoor URL
Connection Steps
Follow the official guide for connecting to remote MCP servers for step-by-step instructions.
- Pro / Max
- Team / Enterprise (Owner)
- Team / Enterprise (Member)
Open Settings Navigate to Settings > Connectors.
Add Custom Connector Click “Add custom connector” at the bottom of the Connectors section.
Configure Connection Enter your MCP server URL (e.g.,
https://{{your-org}}.platform.barndoor.ai/mcp). Optionally, click “Advanced settings” to provide an OAuth Client ID and OAuth Client Secret for your server.Finish Click “Add” to save your connector.
Use in Conversations Start a new conversation — Claude will have access to your connector’s tools and data.
Only Owners can add custom connectors to a Team or Enterprise organization. Members connect individually after an Owner has added the connector.
Open Organization Settings Navigate to Organization Settings > Connectors.
Add Custom Connector Click “Add custom connector” at the bottom of the Connectors section.
Finish Click “Add” to make the connector available to your organization’s members.
Your Owner must add the custom connector to your organization before you can connect to it.
Open Settings Navigate to Settings > Connectors.
Find the Connector Locate the custom connector your Owner added — it will have a “Custom” label.
Connect Click “Connect” to authenticate and start using the connector with Claude.
Use in Conversations Start a new conversation — Claude will have access to your connector’s tools and data.
You can enable or disable specific connectors for individual conversations using the tools menu in the chat interface.
ChatGPT
Prerequisites:
- ChatGPT Plus or Enterprise account
- MCP server OpenAPI schema
Custom GPT with Actions
Follow the official guide for connecting to remote MCP servers.
Create Custom GPT Go to ChatGPT and navigate to Settings → Apps → Create App.
Provide the metadata for your App
- Name – a user-facing title such as Kanban board.
- Description – explain what the connector does and when to use it. The model uses this text during discovery.
- MCP server URL – the public /mcp endpoint of your server (for example https://abc123.ngrok.app/mcp).
Test & Publish Click Create. If the connection succeeds you will see a list of the tools your server advertises. If it fails, refer to the Testing guide to debug your app with MCP Inspector or the API Playground.
Cursor IDE
Prerequisites:
- Cursor IDE installed
- MCP server URL and API key
Open Settings Go to Cursor → Settings (or
Cmd/Ctrl + ,)Find MCP Configuration Navigate to Extensions → MCP or search for “MCP” in settings
Add Server Click Add MCP Server and configure:
{ "mcpServers": { "{{your-org}}.platform.barndoor.ai": { "url": "https://{{your-org}}.platform.barndoor.ai/mcp" } } }Restart Cursor Restart Cursor to apply changes.
VS Code
Prerequisites:
- Visual Studio Code installed
- VS Code version with MCP support enabled
Connection Steps
Open VS Code Settings Open the Command Palette (
Cmd/Ctrl + Shift + P) and select Preferences: Open Settings (JSON).Configure MCP Server Add your MCP server configuration to
settings.json:{ "mcp.servers": [\ {\ "name": "Your Server",\ "url": "https://{{your-org}}.platform.barndoor.ai/mcp"\ }\ ] }Authenticate Authorize Barndoor and Sign in when prompted.
Reload Window Reload VS Code to activate the MCP connection.
Troubleshooting
Connection Failed
- Verify your server URL is correct and accessible
- Check that authentication credentials are valid
- Ensure your MCP server is running and responding to requests
- Check firewall settings if using a self-hosted server
Tools Not Appearing
- Confirm the MCP server is properly registered
- Verify the server’s tools are correctly defined in its schema
- Try disconnecting and reconnecting the server
- Clear cache and restart the client application
Authentication Errors
- Double-check API keys or tokens
- Verify authentication method matches your server’s requirements
- Check if tokens have expired and need renewal
- Ensure proper scopes/permissions are granted
Security Best Practices
Never share your MCP server credentials publicly or commit them to version control.
- Use environment variables for sensitive credentials
- Implement proper authentication and authorization
- Use HTTPS for all MCP server connections
- Regularly rotate API keys and tokens
- Monitor Barndoor server logs