Hosted MCP server/Development

Formcarry MCP server

Hosted at mcp.formcarry.com·Streamable HTTP

Formcarry collects form submissions from any stack with custom form code and styling. Email notifications and auto replies can be configured, and other apps connected. The MCP server manages forms and runs queries over the submissions they collect. Formcarry’s main documentation covers forms and email settings but does not yet publish an MCP page; the endpoint at https://mcp.formcarry.com/mcp was verified by its Bearer-key challenge on 16 November 2026, which asks for Authorization: Bearer fc_live_....

mcp.formcarry.com Streamable HTTP API key (Bearer fc_live_) Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-11-16
About

Where it fits

Teams that want form submissions and form settings available inside an AI assistant.

  • Create a form and set an email notification.
  • Query submissions that match several field values.
  • Add an auto reply for a new form.

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.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Formcarry as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http formcarry https://mcp.formcarry.com/mcp --header "Authorization: Bearer fc_live_YOUR_KEY" --scope project
  2. 02

    Send the credential

    The provider expects the following header. Replace each placeholder with your own key or token before you connect.

    Required headers
    Authorization: Bearer fc_live_YOUR_KEY
  3. 03

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://mcp.formcarry.com/mcp
Host
mcp.formcarry.com · /mcp
Transport
Streamable HTTP
Authentication
API key (Bearer fc_live_)
Server name
formcarry
Listing type
Community or directory listing

The installer uses the server name formcarry. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that formcarry appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Create a form and set an email notification. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.

Provider page available on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

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.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • 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.

Formcarry documentationhttps://formcarry.com/docs