Skip to Content
GlossaryMCP - Glossary

MCP

Back to GlossaryDevelopment

Model Context Protocol — in Rhesis, either importing external knowledge into Sources or connecting AI agents to Rhesis tools (two different uses).

Also known as: Model Context Protocol

Two meanings in Rhesis

1. Knowledge import (this platform feature) — Connect external systems (Notion, GitHub, etc.) to sync content into Sources for test generation. Configure under MCP in the Rhesis UI. See /docs/mcp.

2. Rhesis MCP server (for AI agents) — Cursor, Claude Code, and Telemachus connect to Rhesis to call tools (, , , etc.). This is not the same as importing Notion pages. See Agent Skill.

When an agent doc says "connect the Rhesis MCP server," it means #2, not knowledge import.

Overview

Model Context Protocol (MCP) is an open standard that enables Rhesis to connect to external knowledge sources and tools. Use MCP to import domain context, sync documentation, or integrate with your existing systems.

What MCP Enables

Knowledge Sources:

  • Connect to documentation systems
  • Sync with knowledge bases
  • Import from CMS platforms
  • Access internal wikis

Tool Integration:

  • Query databases
  • Search internal resources
  • Fetch real-time data
  • Execute custom functions

Supported MCP Integrations

  • File System: Read local documentation
  • Git: Connect to repositories
  • Confluence: Import wiki pages (via Atlassian MCP)
  • Notion: Sync knowledge bases
  • GitHub: Access repository content
  • Custom: Build your own MCP server

Using MCP with Rhesis

MCP integration is available through the Rhesis platform interface. You can:

  1. Navigate to your project settings
  2. Configure MCP connections to external sources
  3. Use connected sources for test generation
  4. Keep knowledge synchronized automatically

MCP in the SDK

The SDK includes MCP client capabilities for advanced use cases. For most use cases, use the source specification approach.

Use Cases

  • Documentation Testing: Keep tests aligned with docs
  • Domain Expertise: Import industry knowledge
  • Dynamic Context: Access real-time information
  • Integration: Connect to existing tools

Best Practices

  • Secure credentials: Store access tokens safely
  • Filter content: Import only relevant knowledge
  • Regular syncs: Keep knowledge up to date
  • Version control: Track knowledge changes

Documentation

Related Terms

Terms