Built by people who ship with agents
Your agents can
run the whole
project board.
We kept bolting agents onto tools that only understood people. So we built the other way round: 82 MCP tools, the same ones the interface uses. Claude, Cursor or your own agents open tickets, move them, log time and write the docs — into the same activity log as everyone else. Not an AI tab. The actual board.
no credit card · 14-day trial · your data stays yours
Onboarding runbook, from the last 6 tickets
Waiting on client sign-off
PR is green, ready to merge
Screen share in video calls
Stripe webhook retries
Client portal branding
A stream of recent activity in a Solar workspace. Entries created by AI agents through the MCP interface are marked with an m c p label, alongside actions taken by people.
82
MCP tools
1:1
agent and human permissions
0
seats billed for agents
iOS · Android
native apps
Built for agent work
One API. Your agents and your team share it.
No separate agent API to keep in sync, and no read-only toy version. Point an agent at a project and it works the board the way a teammate would, under that teammate's permissions. When it gets something wrong you can see exactly what it did, because it is in the log with everything else.
claude · connected to solar
create_issue project=TR type=bug
✓ NW-118 created
list_issues status=blocked
3 blocked, oldest 12 days
log_time issue=NW-96 minutes=45
✓ logged
Client portal
Your clients see their half. Only their half.
Invite a client into a project and they get tickets, progress and hours — with internal work, estimates and margin invisible. No second tool to keep in sync, no screenshots pasted into email.
your view
NW-104 Portal branding
NW-105 Internal: rate card
NW-106 Auth refactor
client view
NW-104 Portal branding
NW-106 Auth refactor
Internal work stays hidden
Time tracking
Hours land on the ticket, not in a spreadsheet.
Start a timer from your phone, attribute it when you stop — to an existing ticket, or to a new one written from your notes. Hours roll up per project and per client, ready to invoice.
time logged · this week
One subscription
The stack an agency usually stitches together.
Jira or Linear
tickets, sprints, epics
Harvest or Toggl
time tracking and billing
A second portal tool
client visibility
Notion or Confluence
project knowledge base
and agents don't consume a seat
Why this exists
We run an agency. For years that meant Jira for tickets, Harvest for hours, and a spreadsheet nobody trusted deciding what the client was allowed to see.
Then most of our work started going through agents, and every one of those tools turned out to assume a human was doing the clicking. The AI features that showed up were chat boxes in a sidebar — they could summarise a ticket, but they couldn't move one.
So we built the board we needed: every operation exposed as a tool, agents running under real permissions, and one activity log that doesn't care whether a person or a model did the work. We use it every day to build itself.
— the team at OBH Software, Dublin
Put your agents on the board.
Make a workspace, paste your MCP token into Claude or Cursor, and watch the first ticket move without you touching it.
14-day trial · no credit card · cancel anytime