Skip to main content

​
Overview

MCP lets Happycapy use another set of tools and data inside a Project. You can ask it to look up context, read records, update systems, query databases, or run team-specific actions. You do not need to understand the protocol. Give Happycapy the server setup guide, access details, and goal. Happycapy can inspect what the server provides, explain what access is needed, and use those tools while it works. You can use MCP with public apps like Gmail and Notion, or with internal knowledge bases, databases, CRMs, approval flows, dashboards, operations tools, and legacy APIs.

​
When to use MCP

Use MCP when you want Happycapy to work with a system instead of only working with the files and context already in the session:
  • Search docs, pages, messages, or team knowledge across tools like Notion, Google Drive, Slack, or an internal wiki
  • Read or update email, calendar, CRM, support, ticketing, or project systems
  • Query databases and internal data systems such as Postgres, Supabase, Neon, dashboards, or reporting tools
  • Work with developer and product systems such as GitHub, Linear, logs, issues, or release data
  • Use team-built actions such as approvals, inventory lookup, customer record updates, or report generation
Whether a tool can be used depends on whether it has an MCP server or setup guide you can provide to Happycapy.

​
What MCP can help with

Bring in context

Let Happycapy find relevant docs, tickets, messages, records, or customer notes before it starts the work.

Use approved actions

Ask Happycapy to draft, update, create, assign, comment, sync, or summarize through tools exposed by the server.

Work with internal systems

Connect team-built servers for internal databases, dashboards, approvals, operations, or legacy systems.

Reuse a setup

Keep the server details in a Project so similar workflows can use the same connection later.

​
Before you start

Helpful details:
  • The MCP server link, repository, or setup guide
  • The account, workspace, project, or data source it should use
  • Any login, token, permission, or workspace approval instructions
  • The task you want Happycapy to complete after the server is ready

​
First use

Give Happycapy the server and the goal: 
Set up this MCP server for this Happycapy Project.
Before making changes, tell me what access it needs.
After it is ready, show me the tools it exposes.

MCP server: [link or setup guide]
Goal: [what you want Happycapy to do]

​
Example workflows

Use our Notion MCP server.
Find the latest product launch notes and summarize the open decisions.

Use the Gmail and Calendar MCP server.
Find customer meeting emails from this week and draft a follow-up plan.

Use the internal CRM MCP server.
Look up this customer, summarize recent activity, and draft an account update.

Use the Postgres MCP server.
Query last week's activation data and explain the trend in plain English.

​
Access and permissions

  • Prefer the server’s official login or authorization flow.
  • Use the smallest permission set that can complete the task.
  • Ask Happycapy to list available tools before it starts making changes.
  • For sensitive actions, ask Happycapy to explain what it will read or change before it runs the tool.
  • Confirm the right account and workspace if the server can access company or customer data.

​
Troubleshooting

​
Setup does not work

Share the official setup guide and ask Happycapy to check what step failed.

​
Authentication fails

Check whether the server expects a browser login, token, API key, environment variable, or workspace approval.

​
The expected tool is missing

Ask Happycapy to list the tools the server exposes, then compare that list with the server docs.

​
The result is too broad

Add the workspace, project, data source, record, date range, or output format you expected.

​
For developers

MCP stands for Model Context Protocol. If you are building or choosing a server, use the official MCP documentation as the source of truth.

Model Context Protocol

Read the official MCP documentation and server resources.

​
Next steps

  • Keep the server link, access notes, and workspace details in your Project if you plan to reuse the setup.
  • Use Automations when the same MCP workflow should run on a schedule.