A2A + Windsurf Editor: Complete MCP Integration

A2A is a MCP server that An MCP server that bridges the Model Context Protocol (MCP) with the Agent-to-Agent (A2A) protocol, enabling MCP-compatible AI assistants (like Claude) to seamlessly interact with A2A agents..

When integrated with Windsurf Editor, you can:

• Register and manage A2A agents for communication
• Send messages to A2A agents and handle responses
• Manage asynchronous tasks and retrieve results

This guide provides step-by-step instructions to set up A2A in Windsurf Editor, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• A2A will be fully integrated and operational
• You can use A2A tools directly in Windsurf Editor
• All A2A capabilities will be available for your workflows
• Access to 4 different tools

Prerequisites

Before starting, ensure you have:

• Windsurf Editor installed and configured
• Compatible operating system (Desktop App)

Installation

Step 1: Install A2A

Configuration

Step 2: Configure Windsurf Editor

1. Locate your configuration file:

   • Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
   • macOS: ~/.codeium/windsurf/mcp_config.json
   • Linux: ~/.codeium/windsurf/mcp_config.json

2. Add server configuration:

{
  "mcpServers": {
    "a2a": {
      "command": "a2a",
      "args": []
    }
  }
}

Note: If A2A requires environment variables, add them to the server configuration:
"env": {
  "MCP_TRANSPORT": "streamable-http",
        "MCP_HOST": "0.0.0.0",
        "MCP_PORT": "8080",
        "MCP_PATH": "/api/mcp",
        "MCP_DEBUG": "true"
}

3. Restart Windsurf Editor

Completely quit and restart Windsurf Editor to load the new configuration.

Examples

Once configured, you can use A2A in Windsurf Editor:

Register and Communicate with Agent

Set up communication with an A2A agent

Ask Windsurf Editor: "Register an agent for data analysis tasks and send it a dataset processing request"

Expected Result: Agent registered, task submitted, and task_id returned for tracking

Stream Real-Time Data

Use streaming to get real-time updates from agent

Ask Windsurf Editor: "Stream live updates from the monitoring agent about system metrics"

Expected Result: Continuous stream of system metrics and status updates

Manage Multiple Agents

Coordinate tasks across multiple A2A agents

Ask Windsurf Editor: "List all available agents and distribute parallel processing tasks"

Expected Result: Agent list displayed, tasks distributed, and progress tracked

Handle Task Results

Retrieve and process completed task results

Ask Windsurf Editor: "Get the results from the data analysis task I submitted earlier"

Expected Result: Task results retrieved with processed data and analysis findings

Testing Your Setup

1. Launch Windsurf Editor
2. Verify A2A is available in the tools list
3. Test basic A2A functionality

Troubleshooting

Common Issues

Agent Registration Failed

Symptoms: Registration errors, Agent not found, Connection timeouts

Cause: Network connectivity issues or invalid agent configuration

Solution:

• Check internet connectivity to A2A network
• Verify agent endpoint URLs are correct
• Ensure agent is online and accepting connections
• Check firewall settings and port accessibility

Task Never Completes

Symptoms: Task stuck in pending state, No response from agent

Cause: Agent overload, network issues, or task complexity

Solution:

• Check agent status and availability
• Cancel and resubmit the task
• Break complex tasks into smaller parts
• Try different agent if available

Transport Protocol Errors

Symptoms: Connection refused, Protocol mismatch errors

Cause: Incorrect transport configuration or port conflicts

Solution:

• Verify MCP_TRANSPORT setting matches client expectations
• Check MCP_HOST and MCP_PORT are accessible
• Ensure no port conflicts with other services
• Try different transport mode (stdio, http, sse)

Message Streaming Issues

Symptoms: Broken streams, Incomplete messages, Timeout errors

Cause: Network instability or buffer overflow

Solution:

• Check network stability and bandwidth
• Reduce message frequency or size
• Enable debug logging to trace issues
• Use appropriate buffer sizes for streaming

Tools Not Appearing

Symptoms: Cascade does not see new tools, Hammer icon missing

Cause: Configuration syntax error or server failed to start.

Solution:

• Check the JSON configuration for syntax errors.
• Verify the command (e.g., npx, python) is in your system PATH.
• Check Windsurf logs for MCP connection errors.

Environment Variables

Symptoms: Authentication failed, Permission denied

Cause: Missing API keys in configuration.

Solution:

• Ensure env block is correctly defined inside the server config.
• Restart Windsurf after changing environment variables.

A2A not appearing in Windsurf Editor

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check A2A installation
• Restart Windsurf Editor
• Check logs for error messages

Next Steps

Now that A2A is integrated with Windsurf Editor:

• Explore all A2A capabilities through Windsurf Editor
• Check out other MCP servers that work with Windsurf Editor
• Join the MCP community for tips and support
• Consider contributing to A2A development

Need Help?

• Search for A2A documentation
• Check the Windsurf Editor MCP guide
• Join the MCP community discussions