Ask about the work.
Keep the context.
Connect the assistant your team already uses to Powerlily through MCP, the open standard assistants use to connect to software. It reads only the areas you approve: projects, leads, tasks and the schedule. It cannot change any of them.
An example question
What needs my
attention today?
The assistant looks it up in Powerlily and reads only the areas you approved.
MCP / Powerlily ProSupported read-only tools
An illustration of the connection: your question, your approved access, the record in Powerlily.
Start with your day.
Your assistant looks the answer up in Powerlily instead of asking you to paste it in. Start with the questions your team asks before the trucks leave.
Which leads are mine?
See the leads assigned to you with stage, owner, source and the message they sent in. Open the lead in the CRM when you are ready to act.
How the CRM works ↗What needs my attention?
List overdue tasks with their priority and due date. Pull up the related project when your approved access covers it.
What is on tomorrow?
Check tomorrow’s appointments and crew bookings in your company’s time zone. You see the work your role already sees, nothing wider.
Field operations ↗
A connection you control
You grant the access.
You end it.
Sign in to Powerlily, see the named assistant and the areas it asks to read, then approve or decline. The connection is tied to your staff account and your company. It follows the same record and pricing permissions as your account.
Manage it under Account settings → Connected assistants. Disconnecting stops access and token renewal at once. Any request for wider access needs your approval again.
The current MCP tools are read-only. Changing a record or editing a design still happens in Powerlily. Anything returned to your assistant is then covered by that provider’s own data policies.
- Permission by area
- Projects, leads, tasks, appointments and crew bookings are five separate permissions. You see exactly which ones an assistant asks for before you approve.
- Keep role boundaries
- Approval never widens your role. Every request re-checks your current access to the company and the record.
- Disconnect any time
- See every connected assistant in one list and disconnect any of them, including after a plan change.
- Active Pro access
- MCP connections require an active Powerlily Pro account and a staff sign-in whose role can already see at least one area the assistant asks for.
Registered-client pilot
Pick the assistant.
We register it for you.
Tell us which assistant your team uses. We confirm what it needs and complete the registration. The pilot runs on a registered client ID, Powerlily sign-in and your explicit consent. Compatibility is checked during setup.
Start with one question and the single area it needs. Read what comes back, then approve another area when the team asks for it.
Talk through MCP setup ↗Connection details
- Server address
https://powerlily.io/mcp- Connection
- Streamable HTTP with OAuth sign-in
- Client setup
- Pre-registered client ID, authorization code and S256 PKCE
- Current access
- Approved read-only tools on Powerlily Pro
Once registered, add the server address in your assistant’s integration settings. It is a protocol endpoint, not a page to open in a browser.
MCP, API or Pericles
Choose the connection
for the job.
MCP lets your assistant read. The REST API and signed webhooks let your other systems create and update records and react when a quote is signed or an invoice is paid.
API & integrations ↗Pericles, inside Powerlily
Pericles is the assistant built into the workspace. He answers from your company’s records within your permissions and proposes actions for you to approve. MCP works the other way round: it lets an outside assistant read Powerlily through the access you grant.
Meet Pericles in the workspace ↗Connect your assistant. Ask it what is on tomorrow.
Tell us which assistant your team uses. We’ll register it, show you the read-only tools and set up the first connection with you.
