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

# What is the API route for fetching an MCP server's full details?

> Reference for the API route used to fetch a specific MCP server's configuration by ID in HasMCP.

# API Route for Server Details

## Using HasMCP UI

<img src="https://mintcdn.com/hasmcp/d2X-lsG7b5q-dkAh/images/kb/server-details.png?fit=max&auto=format&n=d2X-lsG7b5q-dkAh&q=85&s=1a3ee76c084bdc80461038d8908979ed" alt="Specific Server Details Page" width="2560" height="1440" data-path="images/kb/server-details.png" />

When viewing a server's details in the UI, the browser internally fetches data from the API to populate the dashboard. You can access the same data programmatically.

## Using REST API

The specific API route to fetch the full details of an individual MCP server is:

**`GET /servers/{id}`**

### Route Details

* **Method**: `GET`
* **Path Parameter**: `id` (string, required) - The exact 11-character identifier of the server you wish to inspect.
* **Response**: Returns a `200 OK` status with a JSON body conforming to the [`GetServerResponse`](/api-reference/servers/get-mcp-server) schema.

This route exposes the complete structure of the specific server, which is essential when auditing a server's provider setup, inspecting its prompt attachments, or verifying its updated configuration version.