Bring your MCP tools into a mobile-accessible assistant

Your assistant can read a repository, inspect documents and query a database. From your phone, you want to ask “What changed on this project?” without opening every tool. A useful hub connects the sources needed for that task and returns a synthesis with accessible evidence.

Know where tools run

The host runs the assistant and connects several MCP servers, each providing its own tools. The Pacerelle MCP server adds mobile inbox and reply tools; it does not automatically discover or replace the others.

The flow is mobile message, Pacerelle inbox, host assistant, authorized tools and sourced reply. The host may use a local or remote model. Conversation encryption does not determine where that host sends content for inference.

Pick one cross-source question

For example: “Prepare the Atlas project update from its notes folder and repository, separating shipped changes from ongoing work.” This requires two specific sources, not broad access to every disk, database and mailbox.

Before connecting a tool, identify what evidence it contributes and how you will verify it. A source that does not help the result mostly adds permissions and opportunities for confusion.

Scope each source separately

• Documents: restrict access to a chosen directory and define read-only versus write access.
• Repository: name the project, inspect its branch and preserve uncommitted changes.
• Database: begin with a read-only account and views containing only relevant data.
• External services: identify the account and separate consultation from sending or publishing.

Enforce these boundaries in the server, destination service and host. “Do not change anything” helps define intent but does not replace technical access controls. The Pacerelle MCP guide covers mobile transport; each tool documents its own access model.

Preserve differences between sources

A meeting note and database state may disagree. Ask the assistant to show each source, date and scope, then identify the discrepancy instead of forcing a certain conclusion.

For the project update, use three sections: shipped with commit references, ongoing according to dated notes and points requiring confirmation. If a local path cannot be opened on mobile, provide an excerpt or authorized attachment.

Test boundaries and failures

Disconnect one source during a trial. The assistant should state what it consulted and what is missing, without silently recycling a previous answer. Ask an out-of-scope question and verify that unauthorized access fails.

Add one source at a time and repeat the same task to see what improves. Before enabling writes, prepare the proposed change and apply the permission rules appropriate to your integration.

This hub still depends on an active assistant session. A dedicated SDK integration may fit permanent, repeatable processing better. Choose based on the actual work: occasional conversation across tools, or an autonomous process with enforced stages.