MCPCloud
A self-hosted MCP gateway that lets you write Python functions and register them as skills to be used as tools by any MCP-compatible client like Claude Desktop or Claude API.
README
MCPCloud
Self-hosted MCP (Model Context Protocol) gateway. Write any Python function, register it as a skill, and it instantly becomes a tool that Claude Desktop, Claude API, Cursor, or any MCP-compatible client can call.
Website: mcpcloud.dev · GitHub: carsor007/mcpcloud
How it works
Claude Desktop / Claude API / any MCP client
↓ MCP tool call
MCPCloud (this repo)
↓ your code runs
Jira · Slack · Salesforce · anything
Every Python function registered as a skill becomes an MCP tool. No vendor lock-in, no proprietary agent framework — just functions.
Quickstart
Run locally with Docker:
git clone https://github.com/carsor007/mcpcloud.git
cd mcpcloud
cp .env.example .env
docker compose up
Open http://localhost:8000/ui — the tool browser shows all registered skills.
Connect Claude Desktop:
curl http://localhost:8000/mcp/jira_ops/config
Paste the returned JSON into ~/Library/Application Support/Claude/claude_desktop_config.json under "mcpServers". Restart Claude Desktop.
Adding a skill
Drop a .py file into skills/. Any file with a register_all() function is loaded automatically on startup.
# skills/my_tools.py
from registry import SkillResult, get_registry
async def my_skill(input: dict, context: dict) -> SkillResult:
'''One-line description shown in the UI.'''
return SkillResult(success=True, output={"result": input.get("text", "")})
def register_all():
get_registry().register(
"my_tools", # agent type — groups skills in the sidebar
"my_skill", # skill name — shown under the group
my_skill,
schema={
"type": "object",
"required": ["text"],
"properties": {
"text": {"type": "string", "description": "Input text"}
}
}
)
Restart the server. The skill appears in the UI and is immediately callable as an MCP tool.
Included skills
Both work out of the box — real API calls run when credentials are configured, stub data is returned otherwise.
jira_ops
| Skill | Description |
|---|---|
create_ticket |
Create a Jira issue with priority, type, and description |
get_ticket |
Fetch status, assignee, and priority by issue key |
search_tickets |
Run a JQL query and return a summary list |
Configure by setting JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN in .env.
slack_ops
| Skill | Description |
|---|---|
send_message |
Post a message to a channel with optional field grid |
alert |
Send an urgent alert with severity badge — critical sends @channel |
Configure by setting SLACK_WEBHOOK_URL in .env.
Deploy to AWS
The Deploy to AWS button above launches a CloudFormation stack in your account. The public image is already hosted — no ECR setup required.
It provisions:
- ECS Fargate — 2 tasks, no EC2 to manage
- ElastiCache Redis — session tracking across workers (~$15/month for t4g.micro)
- Application Load Balancer — with optional HTTPS via ACM
- Secrets Manager — stores Jira, Slack, and API credentials securely
You will need: a VPC with at least 2 public subnets.
One-click deploy (console):
Click the Deploy to AWS button above.
CLI deploy:
cd deploy/aws
make deploy \
VPC_ID=vpc-xxxxxxxxxxxxxxxxx \
PUBLIC_SUBNETS=subnet-aaa,subnet-bbb \
PRIVATE_SUBNETS=subnet-ccc,subnet-ddd
After deployment, retrieve your URLs:
make outputs
Self-hosting your own image (optional — if you've modified the code):
cd deploy/aws
make ecr-public-create # one-time: creates public ECR repo
ECR_PUBLIC_ALIAS=your_alias make push-public
Configuration
| Variable | Required | Description |
|---|---|---|
REDIS_URL |
No | Enables multi-worker session tracking. Set automatically in Docker Compose and CloudFormation. |
JIRA_URL |
No | e.g. https://your-domain.atlassian.net |
JIRA_EMAIL |
No | Atlassian account email |
JIRA_API_TOKEN |
No | Create at Atlassian |
JIRA_PROJECT |
No | Default project key (default: IT) |
SLACK_WEBHOOK_URL |
No | Create at Slack |
ANTHROPIC_API_KEY |
No | Required only by skills that call Claude |
OPENAI_API_KEY |
No | Required only by skills that call OpenAI |
License
Apache 2.0 — see LICENSE.
Free to self-host. Managed deployment available on AWS Marketplace.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。