Documentation Index
Fetch the complete documentation index at: https://mintlify.com/dvlpjrs/guMCP/llms.txt
Use this file to discover all available pages before exploring further.
What is guMCP?
guMCP (Gumloop Unified Model Context Protocol) is an open-source collection of MCP servers that can be run both remotely and locally. The project aims to create the largest collection of MCP servers with a unified backend architecture, fostering a community around AI integrations and the future of AGI.While many MCP server providers are closed source, and open-source alternatives typically only support local hosting through stdio, guMCP provides a comprehensive solution for both deployment models.
Key features
Dual transport support
Run servers locally via stdio or remotely via SSE (Server-Sent Events) transport
Unified backend
Consistent architecture across all servers with shared authentication and initialization patterns
Flexible authentication
Pluggable auth system supporting OAuth 2.0, API keys, and custom implementations via
BaseAuthClientGrowing collection
15+ production-ready servers including Google Workspace, Slack, Linear, Airtable, and more
Available servers
guMCP provides integrations with popular productivity and development tools:Google Workspace
- Google Sheets - Create, read, and update spreadsheets
- Gmail - Send emails and manage inbox
- Google Docs - Create and edit documents
- Google Drive - Manage files and folders
- Google Calendar - Schedule and manage events
Communication & collaboration
- Slack - Send messages, manage channels, and interact with workspaces
- Outlook - Email and calendar management via Microsoft Graph API
Productivity tools
- Airtable - Database operations and workflow automation
- Linear - Issue tracking and project management
- Attio - CRM operations and contact management
- Typeform - Form management and response handling
- QuickBooks - Financial data and accounting operations
- HubSpot - Marketing and sales automation
Search & AI
- Perplexity - AI-powered search and research
Quick start
Architecture
Understand the unified backend structure and how servers are organized
Installation
Set up your development environment and install dependencies
Local deployment
Run servers locally using stdio transport
Remote deployment
Deploy servers with SSE transport for remote access
Authentication models
guMCP supports two primary authentication approaches:Local authentication
For local development and self-hosted deployments, theLocalAuthClient stores credentials and OAuth configurations in local files:
- OAuth configs:
local_auth/oauth_configs/<service_name>/oauth.json - User credentials:
local_auth/credentials/<service_name>/<user_id>_credentials.json
Remote authentication
For hosted deployments, implement a customBaseAuthClient that integrates with your authentication infrastructure. The GumloopAuthClient provides a reference implementation for remote credential management.
Design philosophy
guMCP is built on three core principles:- Unified architecture - Every server follows the same patterns for initialization, tool registration, and credential management
- Transport flexibility - Servers work seamlessly with both stdio and SSE transports without modification
- Open ecosystem - Fully open-source to encourage community contributions and transparency
Community & support
GitHub Issues
Report bugs and request features
Forum
Ask questions and share ideas
Contributing
Learn how to contribute new servers
Security & compliance
Security is our highest priority. Gumloop is SOC 2 Type II, GDPR, and HIPAA compliant. We actively reward responsible disclosure of security vulnerabilities to security@gumloop.com.guMCP is licensed under GNU General Public License v3.0 (GPL-3.0). By contributing, you agree your contributions will be licensed under the same terms.
Next steps
Ready to get started? Here’s what to do next:- Understand the architecture - Read the architecture overview to learn how guMCP is structured
- Install guMCP - Follow the installation guide to set up your development environment
- Run your first server - Try the local deployment guide to run the simple-tools-server
- Explore integrations - Check out server-specific documentation for the services you want to integrate