Connect an AI Assistant to OnRamp (MCP)

What you can do with it

Once your assistant is connected, you ask for work in plain language and it does the clicking for you. It can read, and, where your role allows, change, the same things you work with in OnRamp.

• "Which of my projects are overdue, and who owns them?"

• "Show me everything Acme still has open this week and summarize the last customer comments."

• "Create a project for Globex from the Enterprise Onboarding playbook, owned by me, going live March 14."

• "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 and nudge the people assigned to anything past due."

• "Pull the Project health overview report for last quarter."

Before you connect

Three things have to be true, and the first one is turned on by OnRamp, not by you.

Connect your assistant

Every assistant needs the same address: https://api.onramp.us/mcp. Each person connects their own account, so the assistant always acts as the person who approved it.

1. In your assistant, add a remote MCP server (Claude calls it a custom connector). In Claude on the web or desktop, open Settings, then Connectors, then Add custom connector, name it OnRamp and paste the address.

2. Start the connection. Your browser opens an OnRamp page. Sign in if you are asked to.

3. Check the approval screen. It shows your name, email and organization, and says the assistant will act as you.

4. Select Connect. The assistant now lists the OnRamp tools.

5. Try "Who am I in OnRamp?" to confirm it is working.

In Claude Code, add the server from your terminal, then run /mcp and choose OnRamp to sign in:

claude mcp add --transport http onramp https://api.onramp.us/mcp

Menu names differ between assistants, so look for "remote MCP server", "custom connector" or "integration" if yours is worded differently.

If you select Cancel on the approval screen, nothing is connected and nothing is shared.

What the assistant can do for you

The assistant acts as you and can never do more than your role allows. It sees the projects, accounts, playbooks and tasks you can see, and a change you could not make in OnRamp is refused. If a field is locked or your seat cannot edit it, nothing is saved.

Here is what you can ask for, by area of OnRamp.

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 custom data fields.

• Review the activity feed to see who did what, narrowed to a project, a person, a date range or a kind of change.

Projects

• Find and read. List your projects and filter them by status, owner, overdue or go-live date. Open one to see its dates, owner, account, status, team, portal settings, tags, custom field values and progress by module. Read its notes and comments.

• Start one. Create a project from a published playbook with an owner, an account, dates and team members.

• Keep it current. Rename it, change its description, owner, start or go-live date (and move the open task due dates by the same amount), set custom data fields and tags, mark it complete or reopen it.

• Notes. Add a note, or edit one you wrote.

• Shape the plan. Add library modules, rename a module, and reorder modules and the tasks inside them.

• People. Add or remove team members and customer members, and send project invitations.

Tasks

• Find and read. Find tasks across your projects, open one to see its details, its form questions and its comments.

• Add and edit. Add a task to a module. Change its name, description, assignee, dates, who it is visible to and which roles it is for.

• Move it along. Set a task's status, start it, reopen a finished one or reset it, and make one task wait for another.

• Answer forms. Fill in a form step's answers.

• Talk about it. Comment, reply, and edit your own comments.

• Nudge people. Remind project members about tasks by email, and by text if you ask. It shows you who would be texted before anything goes out.

Customers

• Accounts. List and open accounts, create new ones, edit their details and custom fields, set tags and add notes.

• Customer users. See the customer users on an account, create them, edit them and move them to another account.

Playbooks

• Read. List playbooks and open one to see its modules and tasks.

• Build and edit. Create a new playbook, or open the draft of an existing one. Change its settings, add, rename, reorder and delete modules and tasks, and add library modules.

• Publish stays with you. The assistant works on drafts and gives you a link to review. You publish from OnRamp.

Views and reports

• Views. List the saved views you can open (yours, shared with you, and your organization's), run one, or save a new one. You can run a view with different filters or columns without changing it.

• Reports. Run any of 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.

What stays in OnRamp

Some things are deliberately left out. The assistant cannot archive or unarchive projects, delete projects, accounts or tasks, change a saved view that already exists, or create and edit your internal team members.

Changes that reach other people

A change made through the assistant behaves exactly like the same change made in OnRamp, including the emails, webhooks, automations and CRM updates that follow it.

Using it day to day

Name the project, account or person the way you would to a colleague. The assistant searches OnRamp to find the right one and asks if it is not sure.

• Ask for the plan first on anything big. For bulk edits, or anything that emails customers, ask "tell me what you will change before you do it." Reading is free; changing is what to slow down for.

• Keep the assistant's approval prompts on for changes. Assistants ask before running a tool that changes data. Approve each change, and avoid "always allow" for the OnRamp change tools.

• Ask for the slice you need. For a big portfolio, ask for a filter such as overdue, a status or an owner, or have it run one of your saved views.

• Give reports a date range. The Core Insights reports need a start and end date, for example "last quarter."

• Text nudges show who will be texted. The assistant previews the recipients and the count first. If more people would be texted than you approved, the nudge is refused and nothing is sent.

• Playbook edits land in a draft. The assistant works on a playbook's draft and gives you a link to review it. You publish from OnRamp. This needs playbook versioning on for your organization.

• Saved views are private. A view the assistant saves is only yours until you share it in OnRamp.

There is no undo button. To reverse a change, ask the assistant to check recent activity to see what changed, then set the earlier value back. Emails and customer updates that already went out cannot be recalled.

Manage connections

Each person owns their own connection, and it carries only their role. Your assistant signs in through OnRamp's approval screen, so it never receives your OnRamp password.

Disconnect

To disconnect, remove OnRamp from your assistant's connector or integration settings. OnRamp has no separate disconnect button, because the connection lives in the assistant. Reconnecting later takes the same steps as connecting.

When access ends on its own

For admins

• Control what someone's assistant can do by controlling their role. The assistant has the same permissions as the person, nothing more. Changing a role also ends their current connection.

• Turning MCP on or off is an OnRamp setting for your whole organization. Ask your OnRamp contact or Support. There is no per-tool setting today.

• OnRamp does not list who has connected. To find out who is using it, ask your team.

Limits

If the assistant sends a lot of requests very quickly, it pauses with "MCP request limit exceeded." Wait a minute and it works again.

Anything the assistant reads is shared with the company behind that assistant, so use one your organization has approved for customer data.

Troubleshooting

Still stuck? Contact OnRamp Support with the message you saw and roughly when.