Skip to main content
Talk to your MCP client in normal language. You do not need to name a tool or write JSON: describe the result you want, and the assistant can choose the RaiseGate tools. Naming RaiseGate helps when the client has many connections enabled.

​
Check the connection

Which RaiseGate organisation and member are you connected as? Show me the scopes available to you.
This uses whoami. It is the quickest check after setup and explains why a write may be unavailable.

​
Review the portfolio

Using RaiseGate, brief me on my tracked companies. Start with anything that needs attention, then cover the most important recent signals. Keep it to ten bullets and include the company name, why it matters, and the evidence.
The assistant can combine list_companies, list_signals, and get_signal for detail.
What has changed across my RaiseGate portfolio since 15 September 2026? Separate items that need action from informational updates.
Use an explicit date when the exact reporting window matters. Phrases such as “since Monday” also work, but the client decides how to translate them.
List the biotech companies I track in RaiseGate, grouped by stage. Flag any company whose tracker is partial, errored, or paused.
Other examples: “show pre-seed and seed companies” or “which trackers are paused?”
Give me a full RaiseGate brief on Acme Bio: its latest signal, recent alerts, what we are watching for, and any item that needs follow-up.
Company names can be used directly. If several names match, the assistant will ask which company you mean.

​
Understand signals and alerts

Signals are developments the tracker found. Alerts are the decisions and email outcomes produced by evaluating those signals against your tracking instructions.

​
Triage discovered leads

Show my unreviewed RaiseGate leads. Group them by sector and stage, then recommend which three I should inspect first and explain why. Do not accept or reject anything yet.
Find unreviewed RaiseGate leads discovered around Acme Bio. Show founder, company, stage, sector, and why each may be relevant.
You can also use a founder’s name. If the source is ambiguous, the assistant asks you to choose from the matches.
Open the full RaiseGate record for Jane Doe at Example Labs and summarize the company, founders, stage, and source.
Start tracking the Example Labs lead in RaiseGate.
Before it acts, the assistant must ask what you want RaiseGate to watch for. For example, answer: “Fundraising, enterprise customer wins, and senior commercial hires.” Alerts automatically go to the member attached to the API key.
Reject the Example Labs lead in RaiseGate.
Rejecting changes shared RaiseGate data, so the assistant should ask for confirmation before it acts.

​
Add and manage companies

​
Add a company

Add Example Bio (https://example.bio) to RaiseGate. The founders are Jane Founder and John Cofounder. Ask me for any missing tracking choices before you create it.
The assistant will ask what to watch for, then call add_company. Founder social profiles are optional because RaiseGate enriches missing profiles in the background. It should poll until enrichment and the first tracker run finish. For a company without a public site, say so explicitly:
Add Stealth Robotics to RaiseGate as a stealth company. The founder is Priya Shah. There is no company website yet.

​
Change tracking

For Example Bio in RaiseGate, watch for clinical milestones, new pharma partnerships, and fundraising. Change the cadence to every 3 days and add the tags biotech and portfolio.
You can also ask:
  • “Turn off email alerts for Example Bio but keep flagging important signals.”
  • “Pause tracking Example Bio.” The assistant should confirm first.
  • “Resume tracking Example Bio.”
  • “Refresh Example Bio now, wait for the run to finish, and summarize any new signals.”
  • “Permanently remove Example Bio and its history.” The assistant must confirm because removal cannot be undone.

​
Ask for a recurring workflow

The RaiseGate MCP server performs the data operations; whether a prompt can run on a schedule depends on your MCP client. If your client supports scheduled tasks, a useful instruction is:
Every Monday at 9:00 AM, review RaiseGate signals from the previous seven days, list anything that needs attention, summarize alerts that were sent, and show unreviewed leads. Stay quiet if there is nothing new or actionable.
If scheduling is not supported, save the same text as a reusable prompt and run it when needed.

​
Make the assistant’s behaviour explicit

Add constraints when you want tighter control:
  • Read-only: “Do not change anything in RaiseGate.”
  • No decisions: “Recommend next steps, but do not accept, reject, pause, or remove anything.”
  • Evidence first: “For every claim, include the signal’s evidence and date.”
  • Compact output: “Return a table with company, update, importance, and suggested action.”
  • Full records: “Use full RaiseGate records, not compact list results.”
  • Limit the window: “Only include information since 1 September 2026.”
Your prompt does not override permissions. Write operations still require the relevant key scopes, and keys belonging to viewer members remain read-only.