Connect an AI/MCP client

Oraphim exposes a native MCP service so compatible AI clients can inspect or author the active project through explicit tools. You choose the transport and permission scope; the client does not receive unrestricted desktop access merely because it is connected.

Start in Oraphim

Open AI Connections and confirm MCP access is running. The normal local endpoint uses 127.0.0.1:38777. Keep the service bound to localhost unless you deliberately configure a secure external environment.

Streamable HTTP

For clients that support Streamable HTTP, use:

Name: Oraphim
Transport: Streamable HTTP
URL: http://127.0.0.1:38777/mcp?permission=Admin

For inspection-only work replace Admin with ReadOnly. If the client requires bearer authentication, copy the bearer token from Oraphim, store it in an environment variable such as ORAPHIM_MCP_BEARER_TOKEN, and configure the client to read that variable. Do not paste a secret token into a field that expects an environment-variable name.

STDIO bridge

The Windows installer includes OraphimMcpBridge.exe. A typical configuration launches:

C:\Program Files\Oraphim\OraphimMcpBridge.exe
--permission Admin

Use the installed Oraphim directory as the working directory. The bridge connects to the running local Oraphim MCP service.

First connection test

Start with a read-only request: ask the client to list project resources or report Oraphim MCP diagnostics. Then graduate to one small reversible edit such as creating/renaming an object. Inspect the result in Oraphim, test undo if the tool is undoable, save, reopen, and confirm persistence.

Troubleshooting

If the client cannot connect, verify Oraphim is running, MCP access is enabled, the port is correct, and another process is not occupying it. If a tool is refused, check the session permission scope before assuming the feature is missing.