S

Semaphore MCP Server

MCP discovered

Details
Endpoint
https://mcp.semaphoreci.com/mcp
Transport
streamable-http
Docs
https://docs.semaphore.io/using-semaphore/ai/mcp-server
Authentication
Semaphore MCP OAuth access oauth2 discovered Set up OAuth ↗
OAuth · resolves from well-known metadata

For MCP clients that support remote MCP OAuth, add the MCP server URL https://mcp.semaphoreci.com/mcp in your client and start the sign-in flow. Semaphore says OAuth-capable clients use discovery and dynamic client registration automatically; browser sign-in and consent grant access. If the feature is not enabled for your org, request MCP access per the MCP Server docs.

Semaphore API token bearer discovered Get token ↗
Authorization: Bearer <credential>

Get your token from your Semaphore account profile. In the web app, open your user menu, choose Profile settings, and under API Token use Reset API Token to mint a new one, or visit your Semaphore account page. The same token is used for the REST API, sem, sem-ai, and MCP token auth.

Semaphore service account API token bearer discovered Get token ↗
Authorization: Bearer <credential>

Service accounts must be enabled for your organization; request access via Service Accounts. Then in Semaphore open the organization People page, choose Create Service Account, assign a role, create it, and copy the token when shown. Service account tokens can only be viewed once and are used the same way as user API tokens.