Local MCP

Run approved Python and Node MCP servers on your own computer, with every tool call still checked by the Quilr MCP Gateway. No endpoint agent required.

Local MCP Overview

Local MCP lets an administrator approve a version of a Python or Node MCP server, and lets a user run that server on their own computer. The Quilr MCP Gateway still checks the user's access and every tool call.

Administrator Setup

Approve a local package version, then decide who can use which of its tools. Approval registers a version. It does not install software on anyone's computer and it does not enable tools automatically.

Connect Your AI App

You run one command, approve your computer in the browser, and your permitted local tools appear in your AI app. You do this once per computer, not once per MCP.

Build Your Own Package

A local package definition describes bundled MCP source, not an arbitrary executable command. You ship reviewed source files, a pinned dependency lock and an explicit tool declaration; the connector runs that source on the user's machine.

Troubleshooting

Work down from the symptom you can see. Most issues are access configuration, a runtime version, or a connection that needs re-establishing.