Custom MCP hack: prove one read before enabling the rest

A product or engineering teammate needs the status of an issue in an internal tracker. The tracker isn’t in the connector catalog for Computer, by DevRev, but the team has a remote MCP server for it. How do you make that connection useful without granting more access than the job needs?

Start with a known issue and one read-only tool. Ask the org admin to add the approved server, authenticate your account if needed, and check Computer’s answer against the original issue. That source check – not a connected badge – is the first win.

This is a setup pattern, not an account of a server we installed or a claim that the process takes a particular amount of time.

Is a custom server the right connection?

A custom MCP server lets Computer call the tools exposed by a compatible remote server when needed. It does not make the source’s entire history searchable in Computer. AirSync brings synced data into Computer for ongoing search and reasoning. If the source already has a connector in your catalog, use that route instead of registering it again. Computer’s connector guide explains the difference.

Don’t use the prompt’s “do not change anything” line as your only safeguard. Restrict the available tools first.

What does the admin do?

Adding a custom MCP server is an org-admin action. The published setup instructions direct the admin to Settings → Integrations → AirSyncs, where the connector view offers a custom-server option. The admin supplies the server’s name, URL, slug, description, and supported authentication method, then completes the connection. The documentation uses different labels for the add button, so follow the custom MCP option displayed in your workspace rather than looking for one exact button name.

The server must be compatible with Computer’s connection requirements. The published connector guide describes OAuth or a personal access token in the customer flow; not every remote MCP endpoint or authentication scheme will work. Once the admin adds the server, individuals can configure their own authentication. Do not put a personal token in a shared screenshot.

Before running a prompt, review the server’s Access tab. The documented choices are Always allow, Needs approval, and Block. A prompt cannot override the permissions assigned to a tool. The connector guide covers those modes.

Check the plan before treating this as a self-serve task. The Computer pricing page lists self-serve connectors separately from custom connectors and directs Pro customers to contact sales for custom connectors. Admin rights do not, by themselves, establish plan access.

How do you test a custom MCP server?

Choose an issue you can open in the source system. After the approved server and its read tool are available to your account, adapt this prompt to the tool’s actual name:

“Use [approved read tool] on [connected tracker] to find [known issue] in [project I can access]. Return its current status and a link to the original record. Do not create or change anything.”

This is a prompt template, not a recorded Computer response. Confirm that the intended read tool was called, then open the original issue and compare its status. If the tool returns no item, check your source-account access and the tool’s access setting before widening permissions.

If the result has no source link, open the record directly before relying on the status. A connection is useful only when you can verify the answer that matters.

Quick questions

Can I add a custom server without admin access?

No. An org admin adds an MCP server; after it is available, individuals can configure their own authentication. Give the admin the approved server URL and the one read operation the task needs. Plan access and the server’s authentication requirements may add further steps. Computer’s MCP guide explains the roles.

What if the server connects but the tool is missing?

Ask the admin whether the read operation is exposed and how its access is set. Check that you authorized the correct source account. A server can appear connected without proving that your specific task works. After access is corrected, retry a known issue and compare the answer with the source record.

Is an MCP lookup the same as an AirSync connection?

No. An MCP tool performs a live operation when Computer calls it. AirSync copies selected source data into Computer so it can be searched and reasoned over later. A successful issue lookup does not mean the tracker has been synced. Choose according to whether you need a point-in-time action or searchable history. Computer’s connector guide explains both.

Your next step: Send your admin the name and URL of your approved compatible server and the single read-only tool needed to check a known issue. If your plan does not include custom connectors, review the access options before starting setup.