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.
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
For a complete list of all supported MCP servers, see the Supported MCP Servers page.
Setting Up MCP Servers
Using Pre-configured Servers
Browse the MCP Server Library
Use the search functionality to find the service you need
Configure Connection
Each server shows:
- Base URL for the service
- Required authentication method
- Available transport protocols
- Link to documentation
Connect
Click “Connect via [Auth Method]” to establish the connection
Creating Custom MCP Servers
Basic Configuration
Connect an MCP server outside of the pre-configured ones
Basic Configuration
Connect an MCP server outside of the pre-configured ones
- 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
Local MCP servers are spun up upon sandbox creation and destroyed when the agent has completed the task.
Remote Server Setup
Remote Server Setup
Remote Server Configuration:
- Base URL - The HTTP endpoint for your MCP server
- Authentication - Configure OAuth, Personal Access Token (PAT), or no authentication (for public MCP servers)
- (Optional) Additional Headers - custom MCP servers might have additional header requirements.
Test your remote server endpoint before adding it to ensure connectivity.
API Tokens are stored securely in a vault under standard encryption. For a more details on how we store API tokens, see the Privacy and Security page.
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
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
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 runs for detailed error messages