Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.
AI connections and developer tools

Connect an assistant to Institution’s remote MCP endpoint

Use an MCP client that supports remote Streamable HTTP and OAuth.

Updated 2026-11-11

Add https://mcp.institutionhq.com/mcp in your assistant’s remote MCP or custom integration settings. The client needs Streamable HTTP and OAuth support to complete the connection.

The root address, https://mcp.institutionhq.com, is the permission portal for people to review connections. It is not the same URL as the remote MCP endpoint your assistant calls.

Follow the OAuth sign-in flow, complete authenticator verification if required, choose one company, and review the requested permissions and duration. Confirm that the displayed assistant and return destination are the ones you intended to connect.

After authorizing, return to the assistant and ask it to inspect the available Institution capabilities before starting work. A connected agent remains limited by the company and permissions you approved and your current Institution role. If the client only accepts a static API key and does not support this OAuth flow, do not paste your Institution password or a developer key into an unrelated field; use a compatible connection method.

Was this article helpful?

Tell us whether this answered the question you came with.

Related articles

Still stuck?

Tell us what you were trying to do and where it went wrong. If you are already a client, you can also open a support case from Help and support in your workspace.

We confirm who you are before we change anything on an account.