MCP (Model Context Protocol) is an open standard for connecting AI assistants to other applications. Once connected, you can ask questions like "What does our forecast look like for the next 12 months?" or "Who hasn't filled in their timesheets this week?" and the assistant fetches the answer from wayahead.
The assistant always acts as you. It sees only the data and reports your wayahead account has access to, and admin-only actions stay limited to administrators.
Server URL
Use this address when you add the connector:
https://mcp.wayahead.app
The server uses the Streamable HTTP transport. You don't need to install anything locally.
What is a connector?
A connector is a saved link between your AI assistant and another application. Once added, the assistant can use that application's tools during a chat, without you copying data back and forth.
You add a connector once, sign in once, and then switch it on or off per chat. You can use several connectors together — for example wayahead and Streamtime — and the assistant combines their data in one answer.
Before you connect
When you connect an AI assistant, you’re asking us to share your wayahead data with the provider of that assistant. You choose the provider; they aren’t one of our service providers and we have no agreement with them covering your data. What they do with it is governed by your agreement with them, so check their terms first. Bear in mind your wayahead account holds information about your team, including capacity and timesheets, and your company’s financial figures.
AI assistants can misread requests and produce inaccurate or incomplete output. wayahead isn’t responsible for AI-generated output, so review anything that matters, especially forecasts, financial figures, permission changes and deletions, before you act on it.
Once connected, the assistant can read and change data in wayahead on your behalf, within your own permissions.
Setting up a connector
Every AI app has a slightly different way to configure connectors. Below are the steps to connect to the wayahead MCP in Claude. Make sure you are logged in to wayahead before setting up a new connector.
In Claude, open Settings → Connectors.
Click Add custom connector.
Enter a name, for example
wayahead, and paste the server URL above. Leave the advanced OAuth fields empty.Click Add, then Connect.
Sign in to wayahead when asked, and approve access (see Authentication below).
Back in a chat, open the tools menu and make sure the wayahead connector is switched on.
To test the connection, ask Claude: "Ping the wayahead MCP server." It should reply with a confirmation.
On a Claude Team or Enterprise plan, an organisation owner may need to add the connector first. Each person then connects with their own wayahead login.
Other MCP clients
Any client that supports remote MCP servers with OAuth (for example Claude Code, Cursor or the MCP Inspector) can use the same URL. Clients without OAuth support can use a personal access token instead (see below).
Authentication
Access is always personal, never company-wide. Whichever way you connect, the assistant is linked to your own wayahead user and can only see and do what you can in wayahead: the same reports, the same admin rights. If a colleague wants to use an AI assistant, they connect with their own login or token.
This is different from the company API key used for the wayahead REST API, which gives access to the whole company account.
There are two ways to connect.
Option 1: Sign in with wayahead (recommended)
This is what happens automatically when you click Connect in Claude. No passwords or tokens are copied anywhere.
A wayahead window opens. Sign in if you aren't already.
A consent screen shows which app wants to access your wayahead data.
Click Allow. You're sent back to Claude and the connector shows as connected.
Claude stays connected in the background. If you haven't used the connector for about 90 days, you'll be asked to connect again.
Option 2: Personal access token
Use this for MCP clients that don't support OAuth, or for scripts and testing.
In wayahead, open your Profile and go to the AI Access tab.
Click Generate token and give it a name you'll recognise later, for example
Postman access on my laptop.Copy the token straight away — it is shown only once.
In your MCP client, send it as a request header:
Authorization: Bearer <your token>
Treat this token like a password. You can revoke it at any time from the same AI Access tab.
Manage your AI access
You can see and control everything that has access to your wayahead data in Profile → AI Access. Each list shows only your own connections; other users manage theirs.
List | What it shows | How to remove access |
AI Access Tokens | Personal tokens you generated, with name, created date and last used date | Click Revoke next to the token. Any tool using it stops working immediately. |
Connected Apps | Apps you approved with Connect, such as Claude, with connected-since and last used date | Click Disconnect. The app loses access immediately and must be connected again to be used. |
The tab also shows the server URL with a copy button, so you can connect a new app from there.
Check these lists now and then. If a token or app hasn't been used in a long time, or you don't recognise it, revoke it. Removing the connector in Claude's settings does not by itself remove it from the Connected Apps list.
What you can do
You don't need to call tools by name — just ask in plain language and the assistant picks the right one. Actions marked admin only work if you are a wayahead company administrator.
Area | What you can ask for | Example prompt |
Forecast | 12-month forecast report (sales, cost, contribution), targets, overdue forecasts; add, change or delete forecast items | "Show our projected contribution for the next 12 months against target." |
Staff & timesheets | Staff list with team, role and capacity; timesheet summary (available, target and actual time); resync staff from Streamtime | "How did the design team's logged hours compare to target last month?" |
Revenue recognition | Accruals and deferrals per job, by type and date range | "List all deferrals for June." |
Automated reports | List scheduled email reports; change recipients or frequency; run a report now | "Send this week's timesheet report to me now." |
Users & access | Your profile and permissions; list users; invite a Streamtime team member; change admin rights or report access (admin) | "Give Sarah access to the Finance report." |
Company | Company details and reporting preferences | "What are our forecast tiers?" |
Connection test | Ping | "Ping wayahead." |
wayahead and Streamtime
The wayahead MCP is not a Streamtime MCP. It gives the assistant access to what wayahead adds on top of Streamtime: forecasts, targets, revenue recognition, capacity and automated reports.
For Streamtime data itself — jobs, items, time entries, invoices, quotes, expenses — use the Streamtime MCP. With both connected, the assistant can combine them, for example matching wayahead forecasts with live Streamtime priorities. If you use HubSpot for deals or Xero for budget targets, connect their MCPs too.
Troubleshooting
Problem | What to do |
"Authentication required" or the connector shows as disconnected | Click Connect again in Claude's connector settings and approve access. With a personal token, check it hasn't been revoked. |
The assistant says it isn't allowed to do something | The action needs administrator rights, or your account doesn't have access to that report. Ask a wayahead administrator. |
Forecast answers are missing job or deal details | Connect the Streamtime MCP (and HubSpot or Xero, if used) alongside wayahead. |
A tool listed in this article isn’t available | Start a new chat. If it’s still missing, disconnect and reconnect the wayahead connector in Claude’s settings. |
Staff list looks out of date | Ask the assistant to resync the staff list, or sign in to wayahead, which resyncs it automatically. |
Unexpected results | The MCP server is currently in BETA. If you encounter any unexpected results, please share this with support so we can fix it. |