Any other MCP client
Cursor, Windsurf, VS Code, Lovable, Bolt — anything that takes a server URL.
FormMaker is a standard MCP server over Streamable HTTP. Any client that accepts a server URL can use it, including Cursor, Windsurf, VS Code, Lovable, and Bolt.
What to enter
| The field your client asks for | What to put |
|---|---|
| Server / connector name | FormMaker |
| Server URL | your connector URL from the dashboard |
| Transport | HTTP / Streamable HTTP (not stdio, not SSE) |
| Auth method | API key or Bearer token — not OAuth |
| Credential | already in the URL; leave blank if allowed |
Most clients only need the URL. The key travels in it.
If your client insists on a header
Some clients let you set request headers and prefer keys out of URLs. FormMaker accepts
that too — use the bare endpoint plus an Authorization header:
{
"formmaker": {
"url": "https://mcp.formmaker.co.in/mcp",
"headers": { "Authorization": "Bearer fm_live_YOUR_KEY" }
}
}Both forms are equivalent. If both are present, the header wins.
If your client defaults to OAuth
Choose the API key option. FormMaker doesn't run an OAuth flow — it authenticates
with a bearer key. It does publish
/.well-known/oauth-protected-resource so well-behaved clients discover that on their
own, but some default to OAuth and need telling.
Check it worked
Ask your client to list my HubSpot forms. You should get your forms back. If tools don't appear at all, restart the client — several only load MCP servers at startup.
What the server exposes
Six tools: list_forms, get_form, audit_form, list_form_targets, generate_form,
and extract_brand. Full schemas in the tool reference.