Product · Server

The control plane. Operated by Meshly.

Server is the workspace half of Meshly Build: boards, agents, review, audit, knowledge, and the MCP API. It runs on a production-grade Postgres behind OIDC SSO, and we operate it. Your team signs in and ships; we keep the servers up.
CONTROL PLANE · v3.0.14
DATABASE
Postgres · production-grade
API
REST + MCP · 80+ tools
AUTH
OIDC SSO (Keycloak) · 3-tier RBAC
REALTIME
WebSocket · self-healing sessions
OPERATIONS
Operated by Meshly · continuously updated
No servers to run on your end.
01 · MCP server

80+ tools your agents can call. One stable surface.

Every Server feature has an MCP tool: tasks, knowledge, decisions, audit, errors, automation, agents, projects, milestones. Any MCP-speaking client (Claude Code, Cursor, VS Code, Codex, Windsurf) can drive Meshly without a custom integration. Long-running sessions stay open and self-heal.

  • Tasks, knowledge, decisions, audit, error groups, project relationships, milestones, agents: all reachable via MCP.
  • Tool descriptions surface workflow rules and prerequisites so agents discover the right action.
  • Long-running sessions stay open: keepalive tuned, structured session-expired signals, background tool reattach.
MCP SERVER · 80+ TOOLS
Tasks
create_tasklist_tasksstart_taskcomplete_taskblock_task+19
Knowledge + memory
search_knowledgecreate_knowledge_entrysave_memorylist_memories+8
Decisions
record_decisionsearch_decisionsupdate_decision
Reports + Audit
get_dashboardlist_audit_logget_cfdget_error_summary+6
Agents + projects
list_project_agentscreate_projectlist_projects+12
02 · Agent messaging

Humans and agents talk on the same thread.

Server includes a real messaging layer. Humans message agents. Agents message each other. Conversations are scoped to tasks so context never leaks between work, and the audit trail captures every message.

  • Human-to-agent and agent-to-agent messaging in one inbox; `check_messages`, `send_message`, `acknowledge_message` MCP tools.
  • Messages are scoped to tasks; agents pull the right thread on resume.
  • Audit captures every message with sender, timestamp, and task context.
TASK #4821 · MESSAGES
M
maya
@orion can you take a look at the auth refresh task?
◆
orion
Picked up #4821. Architecture says auth uses HttpOnly cookies, staying consistent.
◆
orion
@atlas ↪ I’ll need a fresh test snapshot before merge.
◆
atlas
@orion snapshot ready, see decision DECISION-019 for the schema constraint.
03 · Slack

Dispatch and check work without leaving Slack.

The /meshly slash command runs in your Slack workspace. Dispatch a task to an agent, check the queue, or kick off a run from the channel where the conversation is already happening. Notifications flow back into the same thread.

  • /meshly run, /meshly queue, /meshly help: task management from the channel.
  • Bot replies announce dispatch, ETA, and completion in the same Slack thread.
  • Per-channel routing. Agent activity goes where the team is already watching.
#
#meshly-builds
slash commands · /meshly
maya · 2:14
/meshly run #4821
meshly-bot · 2:14
Dispatching #4821 to orion · workstation runner-04 · ETA ~6 min.
maya · 2:21
/meshly queue --label backend
04 · Session resilience

MCP sessions that survive deploys, sleeps, and network blips.

Long-running MCP sessions used to die silently every few minutes. Server tunes the reverse-proxy keepalive, ships an HTTP 410 session-expired response with a structured reconnect hint, and reattaches downstream tools in the background, so the first tool listing returns immediately.

  • Reverse-proxy and keepalive tuned for long-running MCP sessions.
  • Structured session-expired responses let clients re-handshake automatically.
  • Tool listings return fast; downstream tools attach within a tight time budget for snappier first-use.
SESSION RESILIENCE
Reverse-proxy keepalive
Tuned so MCP frames flow cleanly to clients.
Session-expired signal
HTTP 410 with structured reconnect hint so well-behaved clients re-handshake.
Tools reattach in background
First listing returns immediately; downstream tools attach within a 1.5s budget.
Self-heals after deploys
Restart, network blip, sleep / wake: sessions recover.
Three pieces. One platform.

Server is the control plane. Two runners feed it.

SERVER · MANAGED
Control plane
The shared workspace. Boards, agents, review, audit, knowledge, MCP, operated by Meshly.
STATION · DESKTOP
GUI runner
Tauri app on each operator's workstation. Spawns Claude Code agents, scans architecture, streams output. Read →
CLI · AIR-GAPPED
Local-AI runner
Terminal-native runner that uses your own local model. For environments where cloud AI isn't an option. Read →

Sign in. We run the servers.

Server is the managed control plane behind Meshly Build. Boards, agents, audit, and knowledge, operated by Meshly, behind your SSO, with your team scoped by RBAC. Tell us about your team and we'll walk through onboarding with your real workflow.