> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pcnaid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Get Pcnaid MCP Hub running and connected quickly.

## Installation

<Tabs>
  <Tab title="Docker (Recommended)">
    The fastest way to get started with Pcnaid MCP Hub is using Docker:

    ```bash theme={null}
    # Run with default configuration
    docker run -p 3000:3000 pcnaidinc/pcnaid-mcp-hub
    ```

    Or mount your custom configuration:

    ```bash theme={null}
    # Run with custom MCP settings
    docker run -p 3000:3000 \
      -v $(pwd)/mcp_settings.json:/app/mcp_settings.json \
      pcnaidinc/pcnaid-mcp-hub
    ```
  </Tab>

  <Tab title="Local Development">
    For development or customization:

    ```bash theme={null}
    # Clone the repository
    git clone https://github.com/PcnaidInc/Pcnaid-MCP-Hub.git
    cd Pcnaid-MCP-Hub

    # Install dependencies
    pnpm install

    # Start development servers
    pnpm dev
    ```

    This starts both backend (port 3001) and frontend (port 5173) in development mode.
  </Tab>

  <Tab title="npm Package">
    Install Pcnaid MCP Hub as a global package:

    ```bash theme={null}
    # Install globally
    npm install -g @pcnaidinc/mcphub

    # Run Pcnaid MCP Hub
    mcphub
    ```
  </Tab>
</Tabs>

## Initial Setup

### 1. Access the Dashboard

Open your browser and navigate to:

```
http://localhost:3000
```

### 2. Login

The default username is `admin`. On first launch, if no `ADMIN_PASSWORD` environment variable is set, a random password is generated and printed to the server logs.

To pre-set the admin password:

```bash theme={null}
# Via environment variable
ADMIN_PASSWORD=your-secure-password docker run -p 3000:3000 pcnaidinc/pcnaid-mcp-hub
```

<Warning>Change the admin password after first login for security.</Warning>

### 3. Configure Your First MCP Server

1. Click **"Add Server"** in the dashboard
2. Enter server details:
   * **Name**: A unique identifier (e.g., `fetch`)
   * **Command**: The executable command (`uvx`)
   * **Args**: Command arguments (`["mcp-server-fetch"]`)
   * **Environment**: Any required environment variables

Example configuration for a fetch server:

```json theme={null}
{
  "name": "fetch",
  "command": "uvx",
  "args": ["mcp-server-fetch"],
  "env": {}
}
```

## Basic Usage

### Connecting AI Clients

Once your servers are configured, connect your AI clients using Pcnaid MCP Hub endpoints:

<Tabs>
  <Tab title="All Servers">
    Access all configured MCP servers: `http://localhost:3000/mcp`
  </Tab>

  <Tab title="Specific Group">
    Access servers in a specific group: `http://localhost:3000/mcp/{groupName}`
  </Tab>

  <Tab title="Individual Server">
    Access a single server: `http://localhost:3000/mcp/{serverName}`
  </Tab>

  <Tab title="Smart Routing">
    Use AI-powered tool discovery: `http://localhost:3000/mcp/$smart`
    <Info>Smart routing requires PostgreSQL with pgvector and an LLM provider (OpenAI or compatible) API key.</Info>
  </Tab>
</Tabs>

### Example: Adding Popular MCP Servers

Here are some popular MCP servers you can add:

<AccordionGroup>
  <Accordion title="Web Fetch Server">
    ```json theme={null}
    {
      "name": "fetch",
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
    ```
  </Accordion>

  <Accordion title="Playwright Browser Automation">
    ```json theme={null}
    {
      "name": "playwright",
      "command": "npx",
      "args": ["@playwright/mcp@latest", "--headless"]
    }
    ```
  </Accordion>

  <Accordion title="Amap Maps (with API key)">
    ```json theme={null}
    {
      "name": "amap",
      "command": "npx",
      "args": ["-y", "@amap/amap-maps-mcp-server"],
      "env": {
        "AMAP_MAPS_API_KEY": "your-api-key-here"
      }
    }
    ```
  </Accordion>

  <Accordion title="Slack Integration">
    ```json theme={null}
    {
      "name": "slack",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-slack"],
      "env": {
        "SLACK_BOT_TOKEN": "your-bot-token",
        "SLACK_TEAM_ID": "your-team-id"
      }
    }
    ```
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Server Management" icon="server" href="/nodes/integrations/pcnaid-mcp-hub/developer/guides/server-management">
    Learn advanced server configuration and management
  </Card>

  <Card title="Group Management" icon="users" href="/nodes/integrations/pcnaid-mcp-hub/developer/guides/group-management">
    Organize servers into logical groups
  </Card>

  <Card title="Smart Routing" icon="route" href="/nodes/integrations/pcnaid-mcp-hub/developer/guides/smart-routing">
    Set up AI-powered tool discovery
  </Card>

  <Card title="API Reference" icon="code" href="/nodes/integrations/pcnaid-mcp-hub/developer/api/index">
    Explore the complete API documentation
  </Card>
</CardGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Server won't start">
    * Check if the MCP server command is accessible in your PATH - Verify environment variables are
      correctly set - Check Pcnaid MCP Hub logs for detailed error messages
  </Accordion>

  <Accordion title="Can't connect from AI client">
    * Ensure Pcnaid MCP Hub is running on the correct port - Check firewall settings - Verify the endpoint
      URL format
  </Accordion>

  <Accordion title="Authentication issues">
    * Verify credentials are correct - Check if JWT token is valid - Try clearing browser cache and
      cookies
  </Accordion>
</AccordionGroup>

Need more help? Visit our [GitHub repository](https://github.com/PcnaidInc/Pcnaid-MCP-Hub) for support!