·3 min read·Ryvos Team

MCP: How Ryvos Connects to Every App You Use

mcpintegrationsannouncement

MCP: How Ryvos Connects to Every App You Use

The Model Context Protocol is changing how AI agents interact with the world. Instead of building custom integrations for every app, MCP provides a universal standard — one protocol, every tool.

Ryvos now supports MCP natively. Here's what that means for you.

What is MCP?

Think of MCP like USB for AI agents. Before USB, every device needed its own cable. MCP does the same thing for AI tools — it creates a single standard that any app can implement.

When your agent needs to read your Gmail, create a Jira ticket, or search your Notion workspace, it doesn't need a custom integration for each one. It just speaks MCP.

How It Works in Ryvos

Add an MCP server to your config:

[mcp.servers.gmail]
transport = { type = "stdio", command = "npx", args = ["@composio/mcp-gmail"] }
 
[mcp.servers.notion]
transport = { type = "stdio", command = "npx", args = ["@composio/mcp-notion"] }

That's it. Restart Ryvos and your agent can now read emails, search documents, and manage pages — all through natural conversation.

Two Transport Types

Stdio — for local tools that run as child processes:

[mcp.servers.filesystem]
transport = { type = "stdio", command = "npx", args = ["-y", "@modelcontextprotocol/server-filesystem", "/home/user/docs"] }

Streamable HTTP — for remote tools running as web services:

[mcp.servers.remote-api]
transport = { type = "sse", url = "https://api.example.com/mcp" }

What You Can Connect

With MCP, the list of available tools grows every week. Some highlights:

  • Google Workspace — Gmail, Calendar, Drive (built into Ryvos)
  • Notion — Pages, databases, search (built into Ryvos)
  • GitHub — Repos, issues, PRs (built into Ryvos)
  • Slack — Messages, channels (built into Ryvos)
  • Linear — Issues, projects (built into Ryvos)
  • Jira — Tickets, sprints (built into Ryvos)
  • Browser — Navigate, screenshot, click, type (built into Ryvos)
  • Databases — PostgreSQL, MySQL, SQLite via MCP servers
  • File systems — Local or remote file access
  • Custom APIs — Any REST API via MCP bridge

Plus hundreds of community-built MCP servers for everything from Stripe to Figma to AWS.

Security

Every MCP tool goes through Ryvos's constitutional safety system. Your agent reasons about whether an action is appropriate before executing it. No tool is blindly trusted just because it's connected.

MCP servers can also be scoped per-tool with timeout limits and optional sandboxing:

[mcp.servers.risky-tool]
transport = { type = "stdio", command = "python3", args = ["tool.py"] }
timeout_secs = 30
tier_override = "t3"

What's Next

We're working on:

  • MCP sampling — let servers request LLM inference through Ryvos
  • Resource subscriptions — real-time updates when connected data changes
  • One-click MCP setup in Ryvos Cloud — connect apps from the dashboard without touching config files

The MCP ecosystem is growing fast. By building on an open standard, every new MCP server automatically works with Ryvos. No updates needed.

Try it now: ryvos mcp add gmail or check the MCP docs.