MCP Server

The Peakwind Model Context Protocol (MCP) server provides a standardized interface that allows any compatible AI model or agent to interact with your Peakwind workspace in a simple and secure way.

Connect to our MCP server natively in Claude, Cursor, and other MCP-compatible clients to enable AI assistants to access workspace information, manage tasks, and collaborate within your Peakwind environment.

Peakwind's MCP server follows the authenticated remote MCP specification, so the server is centrally hosted and managed. The server provides tools, resources, and prompts for interacting with Peakwind workspaces — with more functionality on the way.

Features

• 🔐 Secure Authentication: OAuth 2.1 with dynamic client registration
• 🚀 Multiple Transports: Supports both Server-Sent Events (SSE) and Streamable HTTP
• ⚡ Global Access: Low-latency access from anywhere in the world
• 🛠️ Rich Tool Set: Access workspace data, perform calculations, and more
• 📦 Resources: Query system information and version details
• 💬 Prompts: Pre-configured prompts for common interactions

Endpoints

Our MCP server supports both Server-Sent Events (SSE) and Streamable HTTP transports. Both transports use OAuth 2.1 with dynamic client registration for authentication:

• HTTP: https://mcp.peakwind.dev/mcp
• SSE: https://mcp.peakwind.dev/sse

We recommend using the streamable HTTP endpoint where supported for increased reliability.

Available Tools

get-workspace-info

Get information about the currently connected workspace.

Requirements: Workspace API token authentication

Returns: Workspace details including ID, name, slug, owner, and token information

calculator

Perform mathematical calculations.

Input: Mathematical expression as a string

Returns: Calculation result

echo

Echo back the provided message (useful for testing).

Input: Message to echo

Returns: The same message

get-time

Get the current server time.

Returns: Current timestamp in ISO 8601 format

Available Resources

peakwind://info

General information about the Peakwind platform and MCP server implementation.

peakwind://version

Current version of the MCP server.

Available Prompts

greeting

Generate a friendly greeting message.

Arguments:

• name (optional): Name of the person to greet
• language (optional): Language for the greeting (en, es, fr, de, zh)

Setup Instructions

Claude Desktop

Team, Enterprise (Claude.ai)

1. Navigate to Settings in the sidebar on web or desktop
2. Scroll to Integrations at the bottom and click Add more
3. In the prompt enter:
   • Integration name: Peakwind
   • Integration URL: https://mcp.peakwind.dev/mcp
4. Make sure to enable the tools in any new chats

Free, Pro (Claude desktop app)

1. Open the file ~/Library/Application Support/Claude/claude_desktop_config.json
2. Add the following and restart the Claude desktop app:

{
  "mcpServers": {
    "peakwind": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.peakwind.dev/mcp"]
    }
  }
}

Claude Code

claude mcp add --transport http peakwind-server https://mcp.peakwind.dev/mcp

Then run /mcp once you've opened a Claude Code session to go through the authentication flow.

Cursor

To add the MCP to Cursor, search for Peakwind from Cursor's MCP tools page, or manually configure:

1. Open Cursor Settings
2. Navigate to MCP configuration
3. Add server with URL: https://mcp.peakwind.dev/mcp

Visual Studio Code

1. Press Ctrl/Cmd + P and search for MCP: Add Server
2. Select Command (stdio)
3. Enter the following configuration:

npx mcp-remote https://mcp.peakwind.dev/mcp

4. Enter the name Peakwind and press Enter
5. Activate the server using MCP: List Servers and selecting Peakwind, then Start Server

Alternatively, add to your VS Code settings:

{
  "mcpServers": {
    "peakwind": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.peakwind.dev/mcp"]
    }
  }
}

Windsurf

1. Press Ctrl/Cmd + , to open Windsurf settings
2. Scroll to Cascade -> MCP servers
3. Select Add Server -> Add custom server
4. Add the following:

{
  "mcpServers": {
    "peakwind": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.peakwind.dev/mcp"]
    }
  }
}

Zed

1. Press Cmd + , to open Zed settings
2. Add the following:

{
  "context_servers": {
    "peakwind": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.peakwind.dev/mcp"],
      "env": {}
    }
  }
}

Other Clients

Hundreds of other tools now support MCP servers. You can configure them to use Peakwind's MCP server with the following settings:

• Command: npx
• Arguments: -y mcp-remote https://mcp.peakwind.dev/mcp
• Environment: None

Authentication

OAuth 2.1 Flow

The Peakwind MCP server uses OAuth 2.1 with dynamic client registration for secure authentication. When you first connect, you'll be prompted to authorize the MCP client to access your workspace.

The OAuth metadata is available at:

• https://mcp.peakwind.dev/.well-known/oauth-authorization-server
• https://mcp.peakwind.dev/api/auth/.well-known/oauth-authorization-server

API Token Authentication

For programmatic access, you can authenticate with your own API keys or OAuth access tokens by passing them directly in the Authorization: Bearer <yourtoken> header instead of using the interactive authentication flow.

This allows you to:

• Interact with the MCP server as an app user
• Provide read-only access through a restricted API key
• Integrate with an existing Peakwind OAuth application without an extra authentication hop

Workspace API Tokens

Some tools (like get-workspace-info) require workspace-specific API tokens. You can generate these tokens from your workspace settings in Peakwind.

FAQ

Does the MCP support Streamable HTTP?

Yes, at the https://mcp.peakwind.dev/mcp endpoint.

Can I authenticate with my own API keys?

Yes, the MCP server supports passing OAuth tokens and API keys directly in the Authorization: Bearer <yourtoken> header instead of using the interactive authentication flow.

Why am I seeing an internal server error?

Try clearing saved auth info by running:

rm -rf ~/.mcp-auth

Then attempt to connect again. You may also need to update to a newer version of Node.js if required.

I'm using WSL on Windows and seeing an error

Try connecting using the SSE transport with the following configuration:

{
  "mcpServers": {
    "peakwind": {
      "command": "wsl",
      "args": ["npx", "-y", "mcp-remote", "https://mcp.peakwind.dev/sse", "--transport", "sse-only"]
    }
  }
}

What's the difference between SSE and HTTP transports?

• HTTP (POST): Request-response pattern, better for transactional operations, more reliable
• SSE (GET): Server-Sent Events, better for streaming and real-time updates

We recommend using HTTP transport where supported.

How do I report issues or request features?

Please contact our support team for assistance or to request new features.

API Reference

For detailed API documentation, visit docs.peakwind.dev/api