Hosted MCP server/Productivity

FormaPortal MCP server

Provider setup path

FormaPortal connects an AI assistant to a client portal so routine work happens by asking: pull up a contact or organisation account with its members, notes, onboarding status and history, log a note after a call, or send a reminder without opening the dashboard. There is no shared public endpoint: you copy your portal's MCP address from MCP connections in the FormaPortal dashboard, sign in with OAuth, tick the portals the assistant may use and decide whether it may make changes. Tools that change data are marked, so clients that support it ask before running them, and the connection never exceeds the user's role.

OAuth Server not checked yet Reviewed 2026-11-16
About

Where it fits

Professional services teams that run client portals and want an assistant to handle lookups and notes.

  • Read a contact's history before a call.
  • Log a note after a call.
  • Send a reminder to a client.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Copy your portal's MCP address

FormaPortal does not publish a shared endpoint. Open MCP connections in your FormaPortal dashboard, copy the address shown there, sign in with your FormaPortal account, tick the portals the assistant may use, and decide whether it may make changes.

  1. Open MCP connections

    In the FormaPortal dashboard, open MCP connections and copy your portal's server address.

  2. Add it to your client

    Paste the address into your MCP client's remote connector settings and sign in with OAuth.

  3. Set the limits

    Choose which portals the assistant may use and whether it may make changes. Write tools are marked so clients can ask first.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

FormaPortal documentationhttps://www.formaportal.com/features/mcp-server