> For the complete documentation index, see [llms.txt](https://vibemx.gitbook.io/neuronai-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vibemx.gitbook.io/neuronai-studio/mcp-servers/overview.md).

# Overview

[MCP (Model Context Protocol)](https://modelcontextprotocol.io) servers expose external tools and resources to agents. NeuronAI Studio lets you configure, test, and bind MCP connectors from the UI.

## What MCP adds

| Without MCP                    | With MCP                                          |
| ------------------------------ | ------------------------------------------------- |
| Custom PHP/webhook tools only  | Filesystem, databases, APIs via standard protocol |
| Manual integration per service | Reusable MCP server ecosystem                     |
| Studio-managed tool code       | Remote tool discovery                             |

```mermaid
flowchart LR
    Agent[Agent] --> Resolver[McpToolResolver]
    Resolver --> Stdio[Stdio Transport]
    Resolver --> HTTP[HTTP Transport]
    Stdio --> Server1[npx MCP server]
    HTTP --> Server2[Remote MCP endpoint]
```

## Configuration sources

| Source           | Where                                        |
| ---------------- | -------------------------------------------- |
| Config presets   | `config/neuronai-studio.php` → `mcp_servers` |
| Database records | Studio UI → MCP Servers                      |

Config presets appear in the UI as starting points. Database records support per-environment customization.

## Studio routes

| Route                                    | Purpose                 |
| ---------------------------------------- | ----------------------- |
| `/neuronai-studio/mcp-servers`           | List MCP servers        |
| `/neuronai-studio/mcp-servers/create`    | Create server           |
| `/neuronai-studio/mcp-servers/{id}/edit` | Edit and test discovery |

> **Screenshot pending:** MCP server index page.
>
> Asset path: `docs/assets/screenshots/mcp-servers-list.png` Capture: `/neuronai-studio/mcp-servers` — dark theme, 1440×900

## Bundled config presets

```php
'mcp_servers' => [
    'filesystem' => [
        'transport' => 'stdio',
        'command' => 'npx',
        'args' => ['-y', '@modelcontextprotocol/server-filesystem', storage_path('app')],
    ],
    'telescope' => [
        'transport' => 'http',
        'url' => env('TELESCOPE_MCP_URL', 'http://127.0.0.1:8000/telescope/mcp'),
    ],
],
```

## Security

* **Stdio allowlist** — restrict which commands can spawn MCP processes
* **HTTP tokens** — use `token_env` for authenticated endpoints

See [Stdio & HTTP](/neuronai-studio/mcp-servers/stdio-and-http.md) and [Security & Access](/neuronai-studio/workflows/security-and-access.md).

## Next steps

* [Stdio & HTTP](/neuronai-studio/mcp-servers/stdio-and-http.md)
* [Agent Binding](/neuronai-studio/mcp-servers/agent-binding.md)
* [MCP Endpoints (publish Studio as MCP)](https://github.com/digitalelvis/neuronai-studio/tree/main/docs/guides/mcp-endpoints/overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vibemx.gitbook.io/neuronai-studio/mcp-servers/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.