-
Notifications
You must be signed in to change notification settings - Fork 0
Add MCP Connectors section to echomodel.ai #1
Copy link
Copy link
Open
Description
Problem
The echomodel.ai landing page showcases frameworks and tools but doesn't surface the production MCP connectors that let agents interact with real services. These connectors demonstrate the ecosystem's value beyond infrastructure — they're what end users actually connect to.
Proposal
Add a Connectors section to echomodel.ai between Solutions and Frameworks & Tools. This section should:
- Introduce the Model Context Protocol (MCP) — a brief one-liner explaining that connectors use MCP to give AI agents access to external services.
- Show the MCP icon alongside the section header, if the MCP project's licensing permits (check https://github.com/modelcontextprotocol branding guidelines).
- List these connectors as cards:
| Connector | Repo | Description |
|---|---|---|
| Google Workspace | echomodel/gworkspace-access |
Gmail, Google Drive, Docs, and Chat access for AI agents |
| Monarch Money | echomodel/monarch-access |
Financial data — transactions, accounts, budgets, and recurring items |
| TickTick | echomodel/ticktick-mcp |
Task management — create, update, complete, and organize tasks |
- Card style should match the existing Frameworks & Tools cards (dark background, label badge, title, one-line description).
- Label badge for each card:
connector(new label color — suggest green to differentiate from blue framework/tool labels).
Section ordering after this change
- Solutions (echoskill, echofit hero cards)
- Connectors (new — Google Workspace, Monarch Money, TickTick)
- Frameworks & Tools (mcp-app, gapp, echomodel CLI)
Work breakdown
- Check MCP icon licensing and obtain SVG/PNG if allowed
- Add
label-connectorCSS class (green badge) - Add Connectors section with MCP intro line and 3 cards
- Position between Solutions and Frameworks & Tools
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels