mcp-template
# custom-mcps
<p align="center">
<img src="media/banner.png" alt="2" width="400">
</p>
<p align="center">
<b>Custom MCPs for a wide range of applications.</b><br>
Write an integration once in <code>services/</code> and it ships three ways: a CLI, an MCP server (streamable HTTP at <code>/mcp</code>), and an HTTP API, all over one shared service registry. Gmail is the first.
</p>
<p align="center">
<a href="#key-features">Key Features</a> •
<a href="#architecture">Architecture</a> •
<a href="#quick-start">Quick Start</a> •
<a href="#cli-usage">CLI Usage</a> •
<a href="#adding-commands">Adding Commands</a> •
<a href="#configuration">Configuration</a> •
<a href="manual_docs/deploy.md">Deploy</a> •
<a href="#credits">Credits</a>
</p>
<p align="center">
<a href="https://railway.com/deploy/gmailmcp"><img alt="Deploy on Railway" src="https://railway.com/button.svg" height="32"></a>
<a href="https://render.com/deploy?repo=https://github.com/Edison-Watch/Custom-MCPs"><img alt="Deploy to Render" src="https://render.com/images/deploy-to-render-button.svg" height="32"></a>
</p>
<p align="center">
<img alt="Project Version" src="https://img.shields.io/badge/dynamic/toml?url=https%3A%2F%2Fraw.githubusercontent.com%2FEdison-Watch%2FCustom-MCPs%2Fmain%2Fpyproject.toml&query=%24.project.version&label=version&color=blue">
<img alt="Python Version" src="https://img.shields.io/badge/dynamic/toml?url=https%3A%2F%2Fraw.githubusercontent.com%2FEdison-Watch%2FCustom-MCPs%2Fmain%2Fpyproject.toml&query=%24.project['requires-python']&label=python&logo=python&color=blue">
<img alt="GitHub repo size" src="https://img.shields.io/github/repo-size/Edison-Watch/Custom-MCPs">
<img alt="GitHub Actions Workflow Status" src="https://img.shields.io/github/actions/workflow/status/Edison-Watch/Custom-MCPs/a_test_target_tests.yml?branch=main">
<a href="https://skills.sh/Edison-Watch/Custom-MCPs"><img alt="skills.sh" src="https://skills.sh/b/Edison-Watch/Custom-MCPs"></a>
</p>
---
## Agent Prompt
> Copy and paste this into your AI coding agent (Claude Code, Cursor, Copilot, etc.) to install:
```text
Install the CLI and download the gmail-mcp skill:
uv tool install custom-mcps
curl -fsSL https://raw.githubusercontent.com/Edison-Watch/Custom-MCPs/main/scripts/install-skills.sh -o install-skills.sh
bash install-skills.sh && rm install-skills.sh
```
The official **gmail-mcp** agent skill is self-published on
[skills.sh](https://skills.sh/Edison-Watch/Custom-MCPs). Install it directly with:
```bash
npx skills add Edison-Watch/Custom-MCPs
```
The skill's source of truth lives in [`skills/gmail-mcp/SKILL.md`](skills/gmail-mcp/SKILL.md);
`make sync-skills` mirrors it to the landing page's
`/.well-known/agent-skills/` discovery tree (digest-pinned in `index.json`).
## App Distribution
- MCP server with OAuth
- Claude and ChatGPT connectors
- APIs and SDKs
- Chat interfaces like iMessage and WhatsApp
- A dashboard that uses the same MCP layer
- Open source
## Direction
This repo is being refactored in place from a single Gmail MCP into a **polyglot
monorepo of small, utilitarian, streamable-HTTP MCP servers** that Edison hosts
as first-party, open-source connectors - commodity capabilities (image preview &
hosting, PDF, and more) wired cleanly for the AI era. New servers default to
**TypeScript on Cloudflare Workers** (under `servers/`), while Python / FastMCP
stays first-class for Gmail and heavy-dependency servers. Everything can be
self-hosted or Edison-hosted with per-user auth.
Full plan - topology, runtime choice, MCP-UI, and the Edison auth/catalog
integration - lives in
[`docs/mcp_commodity_fleet_strategy.md`](docs/mcp_commodity_fleet_strategy.md).
## Key Features
| Feature | Stack |
|---|---|
| CLI (auto-discovery commands, global flags, shell completions, self-update) | Typer |
| MCP server (streamable HTTP at `/mcp`, services auto-registered as tools; stdio supported for local dev) | FastMCP |
| HTTP API server (also hosts `/mcp`) | FastAPI + Uvicorn |
| Auth | WorkOS + API keys |
| Payments | Stripe |
| Database + migrations | SQLAlchemy + Alembic |
| Config (YAML + `.env`) | Pydantic-settings |
| LLM inference + observability | DSPY + LiteLLM + LangFuse |
| Testing | pytest + `TestTemplate` |
| Lint / type / dead-code | Ruff + Vulture + ty + import-linter |
| Pre-commit (folder size, ai-writing, agent-config sync) | prek |
| Telemetry | Anonymous, opt-out |
## Architecture
One codebase, three interfaces. Write business logic once in `services/` and it ships as a CLI subcommand, an MCP tool, and an HTTP route - same Pydantic input/output contract everywhere.
```
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ src/cli/app │ │ mcp_server/ │ │ api_server/ │ transport / interface
│ (Typer) │ │ (FastMCP) │ │ (FastAPI) │
└──────┬───────┘ └──────┬───────┘ └──────┬───────┘
│ │ │
└─────────────────┼─────────────────┘
▼
┌───────────────┐
│ services/ │ pure @service functions
│ @service │ (transport-agnostic)
└───────┬───────┘
▼
┌───────────────┐
│ models/ │ Pydantic I/O contracts
└───────┬───────┘
▼
┌────────────┬───────┬────────────┬─────────────┐
│ common/ │ db/ │ utils/llm/ │ src/utils/ │ shared infra
│ (config) │ (ORM) │ (DSPY) │ (logs/theme)│
└────────────┴───────┴────────────┴─────────────┘
```
### MCP UI (optional)
Need elicitation, image output, or an iframe dashboard for an MCP tool? Add an opt-in **enhancer** in `mcp_server/enhancers/`. Enhancers wrap a service for the MCP transport only - the pure service stays untouched and CLI/API consumers are unaffected.
See [`mcp_server/MCP_UI_ARCHITECTURE.md`](mcp_server/MCP_UI_ARCHITECTURE.md) for the full design.
## Quick Start
```bash
uv sync # install deps
uv run edisonmcps --help # see all CLI commands
uv run edisonmcps greet Alice # run a command
uv run edisonmcps init my_command # scaffold a new command
uv run edisonmcps-serve # start the server (HTTP API + MCP at /mcp on one port)
uv run edisonmcps-mcp # legacy: stdio MCP only, for local Claude Desktop / dev
```
## Deploy
One-click deploy to Railway or Render (backend + managed Postgres, migrations run automatically). See **[deployment docs](manual_docs/deploy.md)** for the per-platform setup, the Railway template variable map, and OAuth/secret wiring.
## CLI Usage
Global flags go **before** the subcommand:
| Flag | Short | Description |
|---|---|---|
| `--verbose` | `-v` | Increase output verbosity |
| `--quiet` | `-q` | Suppress non-essential output |
| `--debug` | | Show full tracebacks on error |
| `--format` | `-f` | Output format: `table`, `json`, `plain` |
| `--dry-run` | | Preview actions without executing |
| `--version` | `-V` | Print version and exit |
```bash
uv run edisonmcps --format json config show # JSON output
uv run edisonmcps --dry-run greet Bob # preview without executing
uv run edisonmcps --verbose greet Alice # detailed output
```
## Adding Commands
Drop a Python file in `src/cli/commands/` and it is auto-discovered.
**Single command** - export a `main()` function:
```python
# src/cli/commands/hello.py
from typing import Annotated
import typer
def main(name: Annotated[str, typer.Argument(help="Who to greet.")]) -> None:
"""Say hello."""
typer.echo(f"Hello, {name}!")
```
```bash
uv run edisonmcps hello World # Hello, World!
```
**Subcommand group** - export `app = typer.Typer()`:
```python
# src/cli/commands/db.py
import typer
app = typer.Typer()
@app.command()
def migrate() -> None:
"""Run migrations."""
...
```
```bash
uv run edisonmcps db migrate
```
Or scaffold with: `uv run edisonmcps init my_command --desc "Does something"`.
## Configuration
```python
from common import global_config
# Access config values from common/global_config.yaml
global_config.example_parent.example_child
# Access secrets from .env
global_config.OPENAI_API_KEY
```
CLI config inspection:
```bash
uv run edisonmcps config show # full config
uv run edisonmcps config get llm_config.cache_enabled # single value
uv run edisonmcps config set logging.verbose false # write override
```
[Full configuration docs](manual_docs/configuration.md)
## Credits
This software uses the following tools:
- [Cursor: The AI Code Editor](https://cursor.com)
- [uv](https://docs.astral.sh/uv/)
- [Typer: CLI framework](https://typer.tiangolo.com/)
- [Rich: Terminal formatting](https://rich.readthedocs.io/)
- [prek: Rust-based pre-commit framework](https://github.com/j178/prek)
- [DSPY: Pytorch for LLM Inference](https://dspy.ai/)
- [LangFuse: LLM Observability Tool](https://langfuse.com/)
## About the Core Contributors
<a href="https://github.com/Edison-Watch/Custom-MCPs/graphs/contributors">
<img src="https://contrib.rocks/image?repo=Edison-Watch/Custom-MCPs" />
</a>
Made with [contrib.rocks](https://contrib.rocks).
TDQS
Scored across 50 tools
Many tools are near-duplicates with different names: gmail_archive_thread and gmail_inbox.archive, gmail_mark_thread_done and gmail_inbox.mark_done, gmail_composer.send and gmail_send, settings.subscribe and webhook_subscribe. An agent cannot reliably tell which variant is appropriate for a given request.
Naming is a mix of dot-separated app namespaces (gmail_inbox.set_focus, gmail_composer.save_draft), flat snake_case names (gmail_archive_thread, webhook_subscribe), and inconsistent verb orders. The same operation appears as both gmail_mark_thread_done and gmail_inbox.mark_done, so there is no predictable pattern.
At 50 tools, the surface is far too large for the apparent Gmail-plus-webhooks scope. Many tools are aliases for the same underlying actions split across UI and headless variants, and the set could likely be reduced by more than half.
The underlying workflows are well covered: Gmail connection, inbox reading and triage, draft compose/send/discard, attachments, reply/forward, archive/done/read, watch, a curation ledger, and webhook settings. Minor gaps like permanent trash or expanded label management exist but are not severe.