MCP Server

What It Does

The MCP server gives your coding assistant access to Friday API documentation and context. This is useful when you want an assistant to:

• Look up Friday API endpoint behavior while writing integration code.
• Answer questions about request and response shapes.
• Help debug API calls using the same documentation you would read manually.
• Keep implementation work grounded in Friday API docs instead of guessing from memory.

The server authenticates with your Friday API key.

Use sandbox keys while building. Only use a production key when you intentionally want your tool to work against live production access.

Choose Your Environment

The MCP server can target either environment. Select it with the server query parameter on the URL, and make sure your API key matches the same environment.

Match the URL to the key. A production key with the sandbox URL (or vice versa) will not work. The environment in the URL and the environment of your key must be the same.

MCP Configuration

Use this configuration in tools that support JSON MCP server configuration. This example targets sandbox — swap the URL to ?server=1 and use a production key to target production:

{
  "mcpServers": {
    "Friday": {
      "type": "url",
      "url": "https://docs.fridayapp.com/mcp?server=0",
      "headers": {
        "X-API-Key": "fri_your_key_here"
      }
    }
  }
}

Replace fri_your_key_here with your Friday API key for the matching environment.

Keep keys private. Do not commit configuration files that contain live API keys.

Connect with Cursor

1. Open your integration project in Cursor.
2. Add the MCP configuration to your Cursor MCP config, such as .cursor/mcp.json in the project.
3. Set the url for the environment you want (?server=0 for sandbox, ?server=1 for production) and replace fri_your_key_here with a matching Friday API key.
4. Restart or refresh Cursor's MCP servers.
5. Ask Cursor to use the Friday MCP server when answering questions about the Friday API.

Example .cursor/mcp.json:

{
  "mcpServers": {
    "Friday": {
      "type": "url",
      "url": "https://docs.fridayapp.com/mcp?server=0",
      "headers": {
        "X-API-Key": "fri_your_key_here"
      }
    }
  }
}

Connect with Claude Code

1. Open the project you use for your Friday integration.
2. Add the same mcpServers configuration to your Claude Code MCP configuration for the project.
3. Set the url for the environment you want (?server=0 for sandbox, ?server=1 for production) and replace fri_your_key_here with a matching Friday API key.
4. Restart Claude Code so it loads the new MCP server.
5. Ask Claude Code to use the Friday MCP server when you need Friday API reference context.

Example configuration:

{
  "mcpServers": {
    "Friday": {
      "type": "url",
      "url": "https://docs.fridayapp.com/mcp?server=0",
      "headers": {
        "X-API-Key": "fri_your_key_here"
      }
    }
  }
}

Which API Key Should I Use?

Sandbox and production keys are separate. Use the key that matches the environment in your MCP URL.

Common Pitfalls

• Committing API keys — Keep MCP config files with real keys out of version control.
• Mismatched environment — The ?server= value in the URL and your API key must be for the same environment. A sandbox key with ?server=1 (production) will fail, and vice versa.
• Using the wrong environment — A sandbox key is safest while building. Use production only when you need production context.
• Forgetting to restart the tool — If the MCP server does not appear, restart or refresh your coding tool after editing the config.