Cursor MCP Server Setup: mcp.json, OAuth, and Slack

Last updated: October 15, 2026

Use FORMLOVA from Cursor by checking client access and permissions, registering the official MCP endpoint, authorizing your FORMLOVA account, then inspecting a saved draft. A list of proposed fields in chat is not evidence that a form was created. Begin with one private landing-page feedback draft and verify the saved target.

FORMLOVA registration, drafts and preview are available on Free. The AI client's eligibility, subscription and usage conditions are separate.

Before connecting

• Have a FORMLOVA account with verified email.
• Check the client's MCP support, account eligibility and organization policy.
• Decide whether the setup is personal or shared, and identify the intended form.
• Use the official endpoint below; do not paste credentials into chat or shared configuration.

https://formlova.com/api/mcp

Add the Cursor MCP configuration

Use MCP management under Customize or configure JSON. Project settings live in .cursor/mcp.json; personal global settings use ~/.cursor/mcp.json. Merge into the existing mcpServers object rather than replacing other servers.

{
  "mcpServers": {
    "formlova": {
      "url": "https://formlova.com/api/mcp"
    }
  }
}

Reload the configuration, complete server OAuth, and inspect Agent tool availability and permissions. Start with a form-list request. If tools are absent, check JSON syntax, scope, duplicate names and enabled state.

If you also searched for a Slack MCP server

Adding FORMLOVA does not connect Slack. Configure the official or organization-approved Slack integration separately, with its workspace and permissions. Identify which service performs each action; begin by reading the form and checking the Slack destination separately. A configured MCP connection alone does not create continuous submission forwarding.

After connecting, test a landing-page feedback draft

This is a proposed trial, not an operation or result measured for this rewrite. Use a private test draft first.

Create a private landing-page feedback draft asking for the page viewed, intended information, unclear points and permission for follow-up. Do not require unnecessary contact data. Use short mobile instructions. Show saved fields and preview. Do not change source files, publish or send data to another service.

Before proceeding, check:

• Is there an actual saved form with the intended name, fields and private state?
• Do required rules, logic and completion copy match the purpose?
• Can you check input on mobile and desktop? Preview submission does not test production storage or email delivery.

Move from draft review to publishing

Inspect the saved fields, required rules and choices, then open form and completion previews. Review instructions, consent, intended audience, duplicate prevention and privacy requirements. Request publishing explicitly after the checks; initial review and final publication are separate stages.

Eligible new forms with supported free-text inputs default to sales detection enabled. Review the setting and external-AI processing; disable it when unsuitable. Classification is after storage and excludes paid/selection-only forms.

After publishing, submit authorized test data to verify actual storage, workflow execution and send results separately. Opening preview does not prove live collection or delivery.

Separate operations from plan eligibility

Response statuses are new, in_progress, resolved and spam. Keep business stages such as confirmed or awaiting a reply in retained tags/notes or an external ledger. Preserve existing notes/tags and do not mark unfinished work complete.

MCP email/phone displays are masked. Do not use them as raw recipients or manual joins; use authorized exports, supported response-recipient tools or server-side integration. Free response notifications are a six-hour owner digest and do not consume outgoing-mail quota. They are separate from per-form immediate notification or paid email workflow actions.

Workflow Place prompts do not automatically start continuous monitoring. Distinguish a single run from triggers, schedules and destinations actually saved.

Troubleshoot in order

Check URL, configuration syntax/scope, account, OAuth, enabled tools, form permissions, then feature eligibility. Refresh tool discovery using the client's current official procedure where necessary. After uncertain writes, retrieve the saved object before retrying to avoid duplicate forms or sends.

Questions and next step

Does connecting unlock paid features? No. Connection and feature eligibility are separate; start with the free draft.

Is every client interface identical? The server URL is shared, but permissions, available tools, UI and confirmation behaviour depend on the client/account.

What should I try first? Create the proposed intake, inspect the saved draft and preview, then add only the operations you need.

Current official references

• Cursor official MCP guide
• FORMLOVA setup

Related Guides and References

• Most form tools stop at creation
• official Cursor setup
• Slack Notification + Sheets Log
• ChatGPT form builder guide -- create a private draft from one short prompt
• Review a form before publishing
• How to view, filter, and manage form responses
• How to find and apply Workflow Place recipes from chat
• Claude Desktop FORMLOVA Guide -- From Connector Setup to Form Operations
• Claude Code FORMLOVA Guide -- From One CLI Command to Form Creation, Publishing, and Operations
• Response to HubSpot Contact
• Response to Notion Database
• MCP Form Service Guide -- From AI Creation to Form Operations
• FORMLOVA with ChatGPT Guide -- Developer-Mode Custom Connector to Form Operations
• FORMLOVA with Gemini CLI Guide -- One gemini mcp add Command to Form Operations
• Cursor CLI: MCP
• Slack Developer Docs: Slack MCP Server overview
• Slack Help Center: Guide to Model Context Protocol in Slack
• Model Context Protocol: Introduction

Disclosure and Verification

This guide is written by FORMLOVA's developer. Client connection steps were checked on October 15, 2026 against current official documentation and local setup code; product features were checked against SPEC and plan definitions. Where older local instructions differ, this article follows the current official flow. This rewrite did not execute a new connection, publication or send; the trial request is a proposal.