Integrations
MCP
Create and manage your MCP servers
MCP (Model Context Protocol) servers enable your agents to interact with external services and tools. Palmier provides a comprehensive MCP Server Library with pre-configured servers for popular services, as well as the ability to create custom MCP server configurations.
For a complete list of all supported MCP servers, see the Supported MCP Servers page.
MCP Server Library
The MCP Server Library contains a curated collection of pre-configured MCP servers for popular services across different categories:Development & Code Management
GitHub, Linear, Notion
Project Management
Atlassian, Asana, Monday.com
Communication
Slack
Payment & Analytics
Stripe, Sentry
Databases
Neon, Supabase
AI & Analysis
Deepwiki, Sequentialthinking
Web Automation
Playwright
Cloud Services
AWS CloudWatch Logs
Setting Up MCP Servers
Using Pre-configured Servers
1
Browse the MCP Server Library
Use the search functionality to find the service you need
2
Select Authentication Method
Choose from the available authentication options:
- Remote - HTTP-based server connection
- Local - Command-based server (runs locally)
- OAuth - OAuth authentication flow
- Token Auth - API token-based authentication
- SSE - Server-sent events support
3
Configure Connection
Each server shows:
- Base URL for the service
- Required authentication method
- Available transport protocols
- Link to documentation
4
Connect
Click “Connect via [Auth Method]” to establish the connection
Creating Custom MCP Servers
Basic Configuration
Basic Configuration
- Click “Add MCP Server” from the library interface
- Configure Basic Settings:
- Name - Unique identifier for your MCP server
- Description - Brief description of what the server provides
- Type - Choose between Local or Remote server
Local Server Setup
Local Server Setup
Local Server Configuration:
- Command - The command to start your MCP server (e.g.,
npx @example/mcp-server) - Environment Variables - Add any required environment variables
Ensure the MCP server package is installed locally before configuring the command.
Remote Server Setup
Remote Server Setup
Remote Server Configuration:
- Base URL - The HTTP endpoint for your MCP server
- Authentication - Configure OAuth, Token Auth, or other methods
- Transport - Select transport protocol (SSE, WebSocket, etc.)
Test your remote server endpoint before adding it to ensure connectivity.
Authentication Methods
OAuth Flow
OAuth Flow
For services requiring OAuth (like Linear):
- Select “OAuth” as the authentication method
- You’ll be redirected to the service for authentication
- Complete the OAuth flow in your browser
- Return to Palmier to complete the setup
OAuth tokens may expire and require re-authentication periodically.
Token Authentication
Token Authentication
For API token-based services:
- Obtain an API token from the service
- Select “Token Auth” as the authentication method
- Enter your token in the configuration
- Test the connection
Store API tokens securely as environment variables when possible.
Local Servers
Local Servers
For command-based servers:
- Ensure the MCP server package is installed locally
- Configure the command to start the server
- Set any required environment variables
- Test the local connection
Local servers are generally more secure for sensitive operations.
Best Practices
Agent Specialization Over Generalization
Avoid: Generic Agents with Many MCP Servers
- Don’t create a single agent with 10+ MCP servers
- Agents become overwhelmed with too many capabilities
- Context switching between different tools reduces effectiveness
- Harder to maintain and debug
Recommended: Specialized Agents with Focused MCP Abilities
- Create multiple specific agents with 2-5 relevant MCP servers each
- Each agent should have a clear, focused purpose
- Better performance and more reliable results
- Easier to maintain and optimize
Example Agent Configurations
Development Agent
Focus: Code management, issue tracking, error monitoring
- GitHub MCP server
- Linear MCP server
- Sentry MCP server
Content Management Agent
Focus: Documentation, team communication
- Notion MCP server
- Slack MCP server
Business Operations Agent
Focus: Financial operations, project management
- Stripe MCP server
- Asana MCP server
- Monday.com MCP server
MCP Server Selection Guidelines
Getting Started
Getting Started
- Start Small - Begin with 1-2 MCP servers per agent
- Test Incrementally - Add servers one at a time and test functionality
Performance Optimization
Performance Optimization
- Monitor Performance - Watch for degraded response times with too many servers
- Group Related Services - Combine MCP servers that work well together
- Consider Rate Limits - Some services have API rate limits that affect performance
Security Considerations
Security Considerations
- Environment Variables - Store sensitive tokens and keys as environment variables
- OAuth Tokens - Regularly refresh OAuth tokens as needed
- Access Permissions - Use minimum required permissions for each MCP server
- Local vs Remote - Prefer local servers for sensitive operations when possible
Troubleshooting
Common Issues
Connection Failures
Connection Failures
- Verify API tokens are valid and not expired
- Check network connectivity to remote servers
- Ensure local MCP server packages are properly installed
Authentication Errors
Authentication Errors
- Re-authenticate OAuth connections if expired
- Verify token permissions match required scopes
- Check environment variables are properly set
Performance Issues
Performance Issues
- Reduce the number of MCP servers per agent
- Check for API rate limiting
- Monitor server response times
Getting Help
Documentation
Check the “View Documentation” link for each MCP server for detailed setup instructions
Testing
Test connections individually before combining servers and monitor agent logs for detailed error messages