access_mcp_resource

The access_mcp_resource utility enables Sypha to retrieve data from external resources - such as file contents, API payloads, or documentation - exposed by active Model Context Protocol (MCP) servers.

Parameters

• server_name (required): The identifier of the MCP server providing the data.
• uri (required): The unique URI for the target resource (e.g., docs://developer/reference).

Operational Function

This tool interfaces with your connected MCP environment to pull informational context. Unlike use_mcp_tool, which is designed for executing actions (such as creating a database entry), this utility specifically focuses on gathering the context necessary for Sypha to reason effectively about your project or architecture.

Common Use Cases

• External Integration: Obtaining data from cloud-resident systems like Slack threads or Google Workspace documents.
• Reference Gathering: Accessing technical specifications or domain-specific documentation managed via an MCP server.
• Real-Time Context: Fetching live data from external services through a dedicated MCP adapter.

Security Controls

Sypha operations involving MCP resources require your explicit authorization by default. Access only occurs automatically if you have designated the specific server and URI as "Always Allowed" in your configuration.

Implementation Examples

Retrieving localized weather data

<access_mcp_resource>
  <server_name>environmental-monitor</server_name>
  <uri>weather://location/tokyo/now</uri>
</access_mcp_resource>

Fetching proprietary API specifications

<access_mcp_resource>
  <server_name>internal-repository</server_name>
  <uri>docs://auth-service/v2-spec</uri>
</access_mcp_resource>