MCP Types
Palmier supports two main types of MCP servers, each with different connection methods and authentication options:Local MCP Servers
Local servers run as processes inside the sandbox environment via stdio and cannot be accessed outside of the sandbox. You define the commands which are executed on sandbox start up. Characteristics:- Command-based execution (e.g.,
npx @example/mcp-server) - Runs locally for enhanced security
- Direct process communication
- No network connectivity required
- Environment variables or argument flags for configuration
- Sensitive operations requiring local access
- Development and testing environments
- Services that don’t require remote API access
Remote MCP Servers
Remote servers connect over HTTP/HTTPS and support multiple transport protocols and authentication methods. Transport Protocols:- SSE (Server-Sent Events) - Real-time streaming communication
- HTTP Streamable - HTTP-based streaming for continuous data flow
- OAuth - Secure OAuth 2.0 flow for services like Linear, Sentry.
- PAT (Personal Access Token) - API token-based authentication
- HTTPS endpoint connection
- Managed authentication flows
- Automatic token refresh for OAuth
- Managed personal tokens via Secrets
- Cloud-based services and APIs
- Services requiring OAuth authentication
- Production environments with managed authentication
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
Asana, Monday.com
Communication
Slack
Payment & Analytics
Stripe, Sentry
Databases
MongoDB, 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
Add MCP to Your List
If the remote MCP servers require OAuth, we will redirect you to authorize. Otherwise, the MCP will be added to your list.
3
Configure Setting
Navigate to your MCP and configure the settings:
- For MCP servers that require PAT, you will need to add the header
Authorization: Bearer ${{ secrets.YOUR_KEY }} - You can also configure the environment variables or commands for your local MCP servers, or extra headers for your remote MCP servers.
4
Add MCP to your agent
Once the MCP setting is saved, you can now configure your custom agents to add these MCP servers as tools.
Creating Custom MCP Servers
You can also create your own 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
Remote Server Setup
Remote Server Setup
Remote Server Configuration:
- Base URL - The HTTP endpoint for your MCP server
- Authentication - Configure OAuth, Token Auth, or No Auth.
- Transport - Select transport protocol (SSE, httpstreamable)
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
Token Authentication
Token Authentication
For API token-based services:
- Obtain an API token from the service
- Add the token to your secrets
- Select “Token Auth” as the authentication method
- Enter your secret reference to your token:
${{ secrets.TOKEN }}
Local Servers
Local Servers
We handle the secure connection between the agent and the sandbox, so no authentication is required on your end.If your local server requires secret keys, you should store them in Secrets and reference it.
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
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