Nysa's MCP tools, explained for developers

Nysa's MCP server gives an agent eleven tools: three for meetings, two for people, two for companies, two for your calendar, and two for searching the company brain. Every tool is read-scoped to what the signed-in teammate can already see. Connect any MCP client to https://mcp.usenysa.com/mcp and sign in with Google.

This page lists the tools by name, as published on Nysa's Smithery listing^[1] and server metadata. If you are new to MCP, start with MCP explained for ops teams.

The server in one paragraph

Nysa is a remote MCP server. The transport is streamable HTTP, sign-in is OAuth, and the URL is https://mcp.usenysa.com/mcp. It is also listed in the official MCP Registry as com.usenysa/nysa. Because the agent signs in as a teammate, it sees what that teammate sees. Raw email stays private to its owner, and the team sees the facts drawn from it. More on that in how Nysa keeps private email private.

Meetings

Meetings come from Nysa's notetaker, which joins the calls you choose as a visible participant. Three tools read them.

• search_meetings searches authorized company meetings and returns bounded summaries. Each result carries a title, start time, attendees, related companies, and counts of highlights, decisions and commitments, plus a canonical nysa://meeting/... address.
• get_meeting gets one authorized meeting by its canonical address.
• get_meeting_transcript gets one bounded page of a meeting transcript. It takes a cursor, so an agent can read a long call page by page instead of loading everything at once.

A typical pattern: search for the meeting, read the summary, and only pull the transcript when the agent needs the exact words.

People and companies

Nysa keeps a page for every person and company your team works with.

• search_people searches authorized people by name. It ignores accents and case, requires every word to match, and tolerates small typos.
• get_person gets one person by canonical address.
• search_companies searches authorized companies by name, with the same matching rules, or by domain substring.
• get_company gets one company by canonical address.

The search tools return bounded summaries with addresses. The get tools take an address and return the full page. That two-step shape keeps responses small.

Calendar

• search_calendar lists the calling account's own calendar events in a bounded time range (at most 31 days), optionally filtered by title text.
• get_calendar_event gets one of the calling account's own calendar events by its canonical address.

Note the word "own". Calendar tools return the signed-in account's events, not everyone's.

Company brain search

• search_brain searches authorized company brain facts and entity pages. An optional deep flag allows one bounded retry. If results are thin, the tool description suggests retrying with the identifier alone, using the company instead of the person, or trying the other language, then calling get_person or get_company after a match.
• discover_memory is listed with the same description and parameters as search_brain.

This is the tool to start with when the question is open ended, such as "what did we agree with this customer?". Facts come back with their source: the quote, the date and where it came from. See how Nysa turns meetings into facts.

What about writing?

Agents can write as well as read. Nysa's connect pages say an agent can read and update your private notes, and that it updates Nysa only on request. It cannot send email or edit your calendar. The tools above are the read side. For the write side, we describe only what the site says, so check the connect pages (Claude, ChatGPT) for the current wording.

Connect in a few steps

1. In Claude, open Customize, then Connectors, and search for Nysa. In ChatGPT, open Apps and search for Nysa.
2. Select Connect and sign in with the Google account you use for Nysa.
3. Start a new conversation. The client picks up the Nysa tools automatically.

You need a Nysa account in a company workspace. Full steps are on the Claude page and the ChatGPT page. For any other MCP client, point it at the server URL above. Nysa lists Claude, ChatGPT, Cursor, Codex, OpenClaw and Hermes as agents it works with. Setup for a whole team takes under 5 minutes.

Design choices worth knowing

• Bounded results. Searches return summaries with a limit, and transcripts come in pages. Agents do not get a data dump.
• Addresses, not blobs. Every item has a canonical address, so an agent can search first and fetch second.
• Authorization on every call. Tool descriptions say "authorized" for a reason: results are filtered to what the signed-in teammate can see. Connect pages also say each call is audited.

For what it looks like in practice, see give Claude your team's meeting context and prep customer calls with an AI agent.

FAQ