Azure + OpenCode: Complete MCP Integration

Azure is a MCP server that The Azure MCP Server gives MCP Clients access to key Azure services and tools like Azure Storage, Cosmos DB, the Azure CLI, and more..

When integrated with OpenCode, you can:

• Access Azure functionality through OpenCode

This guide provides step-by-step instructions to set up Azure in OpenCode, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• Azure will be fully integrated and operational
• You can use Azure tools directly in OpenCode
• All Azure capabilities will be available for your workflows

Prerequisites

Before starting, ensure you have:

• OpenCode installed and configured
• Compatible operating system (macOS, Linux, Windows)

Installation

Step 1: Install Azure

Configuration

Step 2: Configure OpenCode

1. Locate your configuration file:

2. Add server configuration:

Configure MCP servers in your `opencode.json` or `opencode.jsonc`:

```json
{
  "mcp": {
    "my-mcp": {
      "type": "local",
      "command": ["npx", "-y", "@modelcontextprotocol/server-everything"],
      "environment": {
        "API_KEY": "$API_KEY"
      },
      "timeout": 5000
    },
    "remote-server": {
      "type": "remote",
      "url": "https://mcp.example.com/sse",
      "headers": {
        "Authorization": "Bearer $API_TOKEN"
      }
    }
  }
}

Disable a server temporarily:

{
  "mcp": {
    "my-mcp": {
      "type": "local",
      "command": ["npx", "-y", "mcp-server"],
      "enabled": false
    }
  }
}

3. **Restart OpenCode**

Completely quit and restart OpenCode to load the new configuration.



## Examples

Once configured, you can use Azure in OpenCode:



## Testing Your Setup

1. Run opencode in terminal
2. Add "use the mcp_name tool" to your prompts
3. Verify tool execution and response



## Troubleshooting

### Common Issues

#### MCP Server Not Loading

**Symptoms:** Server not appearing in tools, Timeout errors, Command not found

**Cause:** Invalid configuration, missing dependencies, or timeout too short

**Solution:**
- Verify command array is correct in opencode.json
- Check environment variables are set properly
- Increase timeout value if server takes longer to start
- Test MCP server command independently in terminal

#### Context Limit Exceeded

**Symptoms:** Context too large errors, Slow responses, Truncated output

**Cause:** Too many MCP servers adding to context

**Solution:**
- Disable unused MCP servers with enabled: false
- Use per-agent tool configuration to limit active MCPs
- Avoid MCP servers that add many tokens (e.g., GitHub MCP)

#### Remote Server Connection Failed

**Symptoms:** Cannot connect to remote MCP, Authentication errors

**Cause:** Invalid URL, missing headers, or network issues

**Solution:**
- Verify remote server URL is correct
- Check authorization headers are properly configured
- Ensure environment variables for tokens are set

#### Azure not appearing in OpenCode

**Symptoms:** Server not listed, Tools not available

**Cause:** Configuration or installation issue

**Solution:**
- Verify configuration syntax
- Check Azure installation
- Restart OpenCode
- Check logs for error messages



## Next Steps

Now that Azure is integrated with OpenCode:

- Explore all Azure capabilities through OpenCode
- Check out other MCP servers that work with OpenCode
- Join the MCP community for tips and support
- Consider contributing to Azure development

## Need Help?

- Search for [Azure documentation](https://www.mcpstack.org)
- Check the [OpenCode MCP guide](https://www.mcpstack.org/clients)
- Join the MCP community discussions