Configuring MCP Servers

Global MCP Server Inclusion Mode

MCP server utilization impacts your token consumption. Sypha provides options to limit or deactivate MCP server features according to your preferences.

1. Select the "MCP Servers" icon from the Sypha extension's top navigation bar.
2. Navigate to the "Configure" tab, then select the "Advanced MCP Settings" link positioned at the pane's bottom.
3. Sypha launches a settings window. Locate Sypha>Mcp:Mode and choose your preferred option from the dropdown menu.

Managing Individual MCP Servers

Every MCP server features a dedicated configuration panel enabling settings modification, tool management, and operation control. Access these settings by:

1. Selecting the "MCP Servers" icon from the Sypha extension's top navigation bar.
2. Finding your desired MCP server in the list and opening it by selecting its name.

Deleting a Server

1. Select either the Trash icon adjacent to the MCP server you wish to remove, or the red Delete Server button located at the MCP server config box bottom.

NOTE: No confirmation dialog appears for deletion

Restarting a Server

1. Select either the Restart button positioned beside the MCP server requiring restart, or the gray Restart Server button at the MCP server config box bottom.

Enabling or Disabling a Server

1. Toggle the switch positioned next to the MCP server for individual enable/disable control.

Network Timeout

Establishing the maximum response wait time following an MCP server tool call:

1. Select the Network Timeout dropdown positioned at the individual MCP server's config box bottom and adjust the duration. The default setting is 1 minute with a range between 30 seconds and 1 hour.

Editing MCP Settings Files

All installed MCP server configurations reside in the sypha_mcp_settings.json file:

1. Select the MCP Servers icon from the Sypha pane's top navigation bar.
2. Navigate to the "Configure" tab.
3. Select the "Configure MCP Servers" button at the pane's bottom.

The file employs JSON format featuring an mcpServers object containing named server configurations:

{
	"mcpServers": {
		"server1": {
			"command": "python",
			"args": ["/path/to/server.py"],
			"env": {
				"API_KEY": "your_api_key"
			},
			"alwaysAllow": ["tool1", "tool2"],
			"disabled": false
		}
	}
}

Example of MCP Server config in Sypha (STDIO Transport)

Understanding Transport Types

MCP accommodates two transport types for server communication:

STDIO Transport

Employed for local servers executing on your machine:

• Communicates through standard input/output streams
• Reduced latency (eliminates network overhead)
• Enhanced security (no network exposure)
• Simpler configuration (no HTTP server requirement)
• Executes as a child process on your machine

For comprehensive information about STDIO transport operation, see MCP Transport Mechanisms.

STDIO configuration example:

{
	"mcpServers": {
		"local-server": {
			"command": "node",
			"args": ["/path/to/server.js"],
			"env": {
				"API_KEY": "your_api_key"
			},
			"alwaysAllow": ["tool1", "tool2"],
			"disabled": false
		}
	}
}

SSE Transport

Employed for remote servers accessed through HTTP/HTTPS:

• Communicates via Server-Sent Events protocol
• Supports hosting on separate machines
• Accommodates multiple client connections
• Demands network access
• Enables centralized deployment and management

For comprehensive information about SSE transport operation, see MCP Transport Mechanisms.

SSE configuration example:

{
	"mcpServers": {
		"remote-server": {
			"url": "https://your-server-url.com/mcp",
			"headers": {
				"Authorization": "Bearer your-token"
			},
			"alwaysAllow": ["tool3"],
			"disabled": false
		}
	}
}

Using MCP Tools in Your Workflow

Following MCP server configuration, Sypha automatically identifies available tools and resources. To utilize them:

1. Enter your request in Sypha's conversation window
2. Sypha identifies when an MCP tool can assist with your task
3. Approve tool usage when requested (or configure auto-approval)

Example: "Analyze the performance of my API" might engage an MCP tool that evaluates API endpoints.

Troubleshooting MCP Servers

Frequent issues and resolutions:

• Server Not Responding: Verify server process status and confirm network connectivity
• Permission Errors: Validate proper API keys and credentials configuration in your mcp_settings.json file
• Tool Not Available: Confirm proper server tool implementation and verify it's not deactivated in settings
• Slow Performance: Consider adjusting the network timeout value for the particular MCP server