### Verify OnlyOneMCP CLI Installation

Source: https://onlyonemcp.com/docs/cli

Checks the installed version of the OnlyOneMCP CLI to confirm successful installation. This command should output the current CLI version.

```bash
mcp --version
```

--------------------------------

### Install OnlyOneMCP CLI with pnpm

Source: https://onlyonemcp.com/docs/cli

Installs the OnlyOneMCP CLI globally using pnpm, a performant package manager for Node.js. This installation makes the 'mcp' command accessible from your command line.

```bash
pnpm add -g @onlyonemcp/cli
```

--------------------------------

### Configure MCP Client with OnlyOneMCP

Source: https://onlyonemcp.com/docs/quickstart

This JSON configuration snippet shows how to add OnlyOneMCP to your MCP client. It specifies the server URL and includes an authorization header with your generated API key. This configuration is compatible with various MCP clients like Claude Desktop, Cursor, and VS Code.

```json
{
  "mcpServers": {
    "onlyonemcp": {
      "transport": "sse",
      "url": "https://mcp.onlyonemcp.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
```

--------------------------------

### Install OnlyOneMCP CLI with yarn

Source: https://onlyonemcp.com/docs/cli

Installs the OnlyOneMCP CLI globally using yarn, an alternative package manager for Node.js. This command enables the 'mcp' command for terminal use.

```bash
yarn global add @onlyonemcp/cli
```

--------------------------------

### Install OnlyOneMCP CLI with npm

Source: https://onlyonemcp.com/docs/cli

Installs the OnlyOneMCP CLI globally using npm, the recommended package manager for Node.js. This command makes the 'mcp' command available in your terminal.

```bash
npm install -g @onlyonemcp/cli
```

--------------------------------

### List Available Tools in OnlyOneMCP

Source: https://onlyonemcp.com/docs/cli

Lists all available tools across all connected servers within the OnlyOneMCP environment. This provides a comprehensive overview of accessible functionalities.

```bash
$ mcp list
Available Tools (24 total)
──────────────────────────
filesystem/read_file
filesystem/write_file
filesystem/list_directory
database/query
database/insert
...
```

--------------------------------

### Start OnlyOneMCP Server Bridge

Source: https://onlyonemcp.com/docs/cli

Initiates a bridge session to forward local MCP servers to the OnlyOneMCP gateway. This allows local tools to be accessed remotely by authenticated clients. The session can be terminated by pressing Ctrl+C.

```bash
$ mcp connect
✓ Connected to OnlyOneMCP gateway
✓ Forwarding 3 local servers
  - filesystem (12 tools)
  - database (8 tools)
  - custom-api (4 tools)
  
Press Ctrl+C to disconnect
```

--------------------------------

### GET /servers

Source: https://onlyonemcp.com/docs/api

List all MCP servers connected to your account.

```APIDOC
## GET /servers

### Description
List all MCP servers connected to your account.

### Method
GET

### Endpoint
`/servers`

### Parameters

#### Query Parameters

There are no query parameters for this endpoint.

#### Request Body

This endpoint does not accept a request body.

### Response

#### Success Response (200)
- **servers** (array) - A list of MCP servers.
  - **id** (string) - The unique identifier for the server.
  - **name** (string) - The name of the server.
  - **status** (string) - The current connection status of the server.
  - **tools_count** (integer) - The number of tools associated with the server.
  - **created_at** (string) - The timestamp when the server was created.
- **total** (integer) - The total number of servers found.

#### Response Example
```json
{
  "servers": [
    {
      "id": "srv_xxxxx",
      "name": "My Local Server",
      "status": "connected",
      "tools_count": 12,
      "created_at": "2024-01-15T10:30:00Z"
    }
  ],
  "total": 1
}
```
```

--------------------------------

### Authenticate with OnlyOneMCP CLI

Source: https://onlyonemcp.com/docs/cli

Logs the user into their OnlyOneMCP account using OAuth authentication, which typically opens a browser window. Successful authentication grants access to OnlyOneMCP services via the CLI.

```bash
$ mcp login
Opening browser for authentication...
✓ Successfully authenticated as user@example.com
```

--------------------------------

### Display OnlyOneMCP Connection Status

Source: https://onlyonemcp.com/docs/cli

Shows the current connection status and health of bridged servers managed by OnlyOneMCP. It provides details on gateway connectivity, latency, and the status of active servers and their tools.

```bash
$ mcp status
OnlyOneMCP Status
─────────────────
Gateway:    ✓ Connected (eu-west-1)
Latency:    12ms
Servers:    3 active

Active Servers:
  ✓ filesystem    12 tools    connected
  ✓ database      8 tools     connected
  ✓ custom-api    4 tools     connected
```

--------------------------------

### GET /health

Source: https://onlyonemcp.com/docs/api

Check the health status of the OnlyOneMCP gateway.

```APIDOC
## GET /health

### Description
Check the health status of the OnlyOneMCP gateway.

### Method
GET

### Endpoint
`/health`

### Parameters

#### Query Parameters

There are no query parameters for this endpoint.

#### Request Body

This endpoint does not accept a request body.

### Response

#### Success Response (200)
- **status** (string) - The health status of the gateway (e.g., "healthy").
- **latency_ms** (integer) - The latency of the gateway in milliseconds.
- **region** (string) - The geographical region of the gateway.

#### Response Example
```json
{
  "status": "healthy",
  "latency_ms": 12,
  "region": "eu-west-1"
}
```
```

--------------------------------

### Log out from OnlyOneMCP CLI

Source: https://onlyonemcp.com/docs/cli

Clears local credentials and disconnects the CLI from the OnlyOneMCP service. This action revokes access and terminates any active sessions.

```bash
mcp logout
```

--------------------------------

### Check OnlyOneMCP Gateway Health via REST API

Source: https://onlyonemcp.com/docs/api

Query the health status of the OnlyOneMCP gateway. This GET request returns the current status, latency in milliseconds, and the region of the gateway. It's useful for monitoring the API's operational state.

```http
GET /health
```

```json
{
  "status": "healthy",
  "latency_ms": 12,
  "region": "eu-west-1"
}
```

--------------------------------

### POST /servers

Source: https://onlyonemcp.com/docs/api

Register a new MCP server manually.

```APIDOC
## POST /servers

### Description
Register a new MCP server manually.

### Method
POST

### Endpoint
`/servers`

### Parameters

#### Path Parameters

There are no path parameters for this endpoint.

#### Query Parameters

There are no query parameters for this endpoint.

#### Request Body
- **name** (string) - Required - The name of the server to register.
- **url** (string) - Required - The URL of the MCP server.
- **transport** (string) - Required - The transport protocol to use (e.g., "sse").

### Request Example
```json
{
  "name": "Production Server",
  "url": "https://my-mcp-server.com/mcp",
  "transport": "sse"
}
```

### Response

#### Success Response (200)

*(Note: The response for POST /servers is not explicitly defined in the provided text. Assuming a success response would indicate successful registration, possibly with the newly created server's details or a success message.)*

#### Response Example
*(Example assuming a response structure similar to other endpoints or a confirmation message)*
```json
{
  "success": true,
  "message": "Server registered successfully",
  "server_id": "srv_yyyyy"
}
```
```

--------------------------------

### Register New MCP Server via REST API

Source: https://onlyonemcp.com/docs/api

Manually register a new MCP server to your account. This POST request requires a JSON body containing the server's name, URL, and transport protocol. Ensure the provided URL is accessible and the transport is correctly specified.

```http
POST /servers
```

```json
{
  "name": "Production Server",
  "url": "https://my-mcp-server.com/mcp",
  "transport": "sse"
}
```

--------------------------------

### DELETE /servers/:id

Source: https://onlyonemcp.com/docs/api

Remove a server from your account. This action is irreversible.

```APIDOC
## DELETE /servers/:id

### Description
Remove a server from your account. This action is irreversible.

### Method
DELETE

### Endpoint
`/servers/:id`

### Parameters

#### Path Parameters
- **id** (string) - Required - The unique identifier of the server to remove.

#### Query Parameters

There are no query parameters for this endpoint.

#### Request Body

This endpoint does not accept a request body.

### Response

#### Success Response (200)
- **success** (boolean) - Indicates if the operation was successful.
- **message** (string) - A message confirming the server deletion.

#### Response Example
```json
{
  "success": true,
  "message": "Server deleted successfully"
}
```
```

--------------------------------

### Authentication

Source: https://onlyonemcp.com/docs/api

All API requests require authentication via Bearer token. Include your API key in the Authorization header.

```APIDOC
## Authentication

All API requests require authentication via Bearer token. Include your API key in the Authorization header:

`Authorization: Bearer mcp_sk_live_xxxxxxxxxxxx`

**Valid Token**

Returns 200 OK with requested data

**Invalid Token**

Returns 401 Unauthorized error
```

--------------------------------

### List MCP Servers via REST API

Source: https://onlyonemcp.com/docs/api

Retrieve a list of all MCP servers connected to your account. This endpoint returns server details including ID, name, status, tools count, and creation timestamp. It requires a valid Bearer token for authentication.

```http
GET /servers
```

```json
{
  "servers": [
    {
      "id": "srv_xxxxx",
      "name": "My Local Server",
      "status": "connected",
      "tools_count": 12,
      "created_at": "2024-01-15T10:30:00Z"
    }
  ],
  "total": 1
}
```

--------------------------------

### Authenticate API Requests with Bearer Token

Source: https://onlyonemcp.com/docs/api

All API requests to OnlyOneMCP require authentication. This is achieved by including your API key as a Bearer token in the `Authorization` header. Invalid tokens will result in a 401 Unauthorized error, while valid tokens return a 200 OK response.

```text
Authorization: Bearer mcp_sk_live_xxxxxxxxxxxx
```

--------------------------------

### Remove MCP Server via REST API

Source: https://onlyonemcp.com/docs/api

Delete a specific MCP server from your account using its unique ID. This DELETE request is irreversible and will permanently remove the server's registration. A success response indicates the server was deleted.

```http
DELETE /servers/:id
```

```json
{
  "success": true,
  "message": "Server deleted successfully"
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.