Connect an AI tool to OnRamp (MCP)
Updated
Who can do this: Super Admins, Creators, Contributors, Collaborators and Integrators
When you connect an AI tool to OnRamp through MCP, you can ask it for OnRamp work in plain language. It acts as you, with the same access your seat license gives you in OnRamp.
This feature is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.
Before you begin
MCP must be turned on for your organization. We turn it on per organization. If it's off, your assistant shows
MCP tools are disabled for your organization.Ask your OnRamp contact or Support to turn it on.You need a seat in your OnRamp organization. Any seat license can connect. Customer users can't.
Your assistant must be able to connect to a remote MCP server and sign in to it. Check your assistant's own documentation for how it does this.
What you can do with it
Once your assistant is connected, you can ask for things like these:
"Which of my projects are overdue, and who owns them?"
"Create a project for Globex from the Enterprise Onboarding playbook, owned by me."
"Set the Contract Value field to $48,000 on the Initech project and add a note about the call."
"Run my At-risk projects view."
"Pull the Project health overview report for last quarter."
Connect your assistant
Every assistant uses the same address: https://api.onramp.us/mcp. If your organization is hosted in OnRamp's EU region, use https://eu.api.onramp.us/mcp. Each person connects their own account, so the assistant always acts as the person who approved it.
In your assistant, add a remote MCP server and enter the address. Assistants word this differently, for example "custom connector" or "integration."
Start the connection. Your browser opens an OnRamp page. Sign in if you're asked to.
On the approval screen, check your name, email and organization. The screen says the assistant will act as you in OnRamp.
Select Connect.
If you select Cancel on the approval screen, nothing is connected.
If MCP is off for your organization, your browser shows a short error response with the code mcp_disabled instead of the approval screen. It contains the message MCP tools are disabled for your organization. Contact your OnRamp administrator to enable this feature.
What the assistant can do for you
The assistant acts as you and can't do more than your seat license allows. It sees only what you can see in OnRamp. If a field is locked or your seat license can't edit it, the change is refused and nothing is saved.
Look things up
Search by name or text across projects, playbooks, modules, tasks, accounts, people, comments and notes.
See your workspaces, team members, project and task statuses, tags, project roles, library modules and data fields.
Review the activity feed, narrowed to a project, a person, a date range or a kind of change.
Projects
Find and read. List and filter your projects, and open one to read its details.
Start one. Create a project from a published playbook.
Keep it current. Change its name, description, owner and dates. When you move dates, you can shift open task due dates by the same number of days. Set data fields and tags, and mark it complete or reopen it.
Notes. Add a note, or edit one you wrote. Notes written by someone else can't be edited.
Shape the plan. Add library modules, rename modules and tasks, and reorder them.
People. Add or remove project members and send project invitations.
Tasks
Find and read. Find tasks and open one to see its form questions and comments.
Add and edit. Add a task to a module. Change its name, description, assignee, dates, visibility to customers and roles.
Move it along. Set a task's status, start it, reopen it or reset it.
Dependencies. Make one task wait for another, or stop it waiting. When you remove a task's last unfinished blocker, the task is unblocked and its assignee and restricted users are emailed.
Answer forms. Fill in a form's answers.
Comments. Comment, reply, and edit comments you wrote.
Nudge people. Remind project members about tasks by email, and by text only if you ask. The assistant previews who would be texted first. If more people would be texted than you approved, the nudge is refused and nothing is sent.
Accounts
Accounts. List and open accounts, create them, edit their details and data fields, set tags and add notes. Archived accounts can't be edited.
Customer users. See, create and edit the customer users on an account, and move them to another account. Moving a customer user ends their memberships on projects of their previous account.
Playbooks
Read. List playbooks and open one to see its modules and tasks.
Build and edit. Create a playbook, or open the draft of an existing one. Change its settings, add, rename, reorder and delete modules and tasks, and add library modules.
Playbook tasks. A playbook task has roles and day offsets from the project start, not an assignee and dates.
Publishing stays in OnRamp. The assistant gives you a link to review the draft. You publish it from OnRamp.
Views and reports
Views. List your own views, views shared with you and your organization's public views. Run one, or run it with different filters, columns or sort without saving anything. You can also save a new view. It's private to you until you share it in OnRamp.
Reports. Run ten Core Insights reports: Project schedule timeline, Customer task feedback, Owner workload, Pipeline flow analysis, Playbook duration performance, Portal engagement, Project health overview, Project velocity, Task performance and User engagement. Most need a date range. Customer task feedback, Project health overview and Task performance accept one but don't need it.
What stays in OnRamp
The assistant can't archive or unarchive projects, or delete projects, accounts or project tasks. It never changes a saved view that already exists. It can delete tasks and modules in a playbook draft.
Changes that reach other people
A change made through the assistant sends the same emails, webhooks, automations and CRM updates as the same change made in OnRamp.
When the assistant... | What happens |
|---|---|
Creates a project | The owner is emailed. Members are invited only if you ask. Project-created webhooks and automations run. |
Changes a go-live date | The project's customers are emailed. |
Changes a project owner | The new owner is emailed. |
Marks a project complete | The project's customers are emailed and completion automations run. |
Adds a project note | The project owner, internal members and anyone @mentioned are notified. |
Adds a task comment | The people @mentioned, the task's assignee and restricted users and the project owner are emailed. Customers are emailed only when the thread is visible to them. |
Sets a data field synced to a CRM | The value is written to the CRM and data field automations run. |
Nudges people about tasks | They get an email, and a text if you asked for one. Each nudge sends again. |
Using it day to day
Ask for the plan first on anything big. For bulk edits, or anything that emails customers, ask the assistant to say what it will change before it does it.
Ask for the slice you need. For a big portfolio, ask for a filter such as overdue or an owner, or run one of your saved views.
Give reports a date range, for example "last quarter."
To reverse a change, ask the assistant to check the activity feed for what changed, then set the earlier value back. Emails that already went out stay sent.
Anything the assistant reads is shared with the company behind that assistant, so use one your organization has approved for customer data.
Manage connections
Each person owns their own connection. The assistant signs in through OnRamp's approval screen, so it never receives your OnRamp password.
Disconnect
To disconnect, remove OnRamp from your assistant's settings. To reconnect later, follow the steps in Connect your assistant again.
When access ends on its own
What happens | Result |
|---|---|
30 days pass without the connection being used | It ends. If the assistant asks to stay connected, normal use keeps it alive, and the approval screen says it stays connected while the assistant uses it. If the assistant doesn't ask, the connection can't be renewed, so you connect again sooner. |
The person's seat license changes | It ends. They connect again to pick up the new permissions. |
The person is deactivated or deleted | It ends. |
OnRamp turns MCP off for your organization | The tools stop working, and connections can't be renewed while MCP is off. Connections are kept and work again if MCP is turned back on within 30 days of their last use. Otherwise, connect again. |
To control what someone's assistant can do, change their seat license. The assistant has the same permissions as the person, and changing the seat license ends their current connection.
Troubleshooting
What you see | What to do |
|---|---|
| MCP is off for your organization. Ask your OnRamp contact or Support to turn it on. |
The assistant asks you to sign in again | Your connection ended. Connect again from the assistant. |
You can't get past the sign-in or approval screen | Only people with a seat in your organization can connect. Check that you're signed in to OnRamp with your team account, not as a customer user. |
A change is refused and nothing is saved | Your seat license can't make that change, or the field is locked. Make the change in OnRamp or ask a Super Admin. |
The assistant can't find a project or account | Check that you can open it in OnRamp. The assistant sees only what you can see. |
A playbook edit is refused | The playbook isn't a draft, it's archived, that version was superseded, or someone else is editing the draft in OnRamp. Adding or deleting a task in a library-linked module is also refused. Unarchive the playbook in OnRamp, or wait until the other person finishes. |
The assistant says it can't archive a project or delete something | Those actions aren't available through the connection. Do them in OnRamp. |
Still stuck? Contact OnRamp Support with the message you saw and roughly when it appeared.