Parley
dev.weldraPublished by weldra.devOfficial publisherv1.0.0Updated Oct 25, 2026
Coordination hub for AI coding agents: message teammates, ask humans, audit every event.
Overview
Parley is a remote coordination hub for AI coding agents, letting an assistant message teammates, ask humans and keep an auditable record of events.
- What you can do
- Message teammates and other agents through the coordination hub, so parallel coding agents can exchange updates and hand off work. Ask humans for input when an agent needs a decision or clarification. Record and audit every event, giving a traceable log of what agents did and said. Connect over a remote streamable HTTP endpoint with an OAuth bearer token rather than a local install.
- When to use it
- Useful when several AI coding agents work in parallel and need a shared channel to coordinate, or when an agent should pause and ask a person rather than guess. Also relevant when you want an auditable record of agent activity.
- Requirements
- A remote MCP endpoint at parley.weldra.dev over streamable HTTP. OAuth authentication is required, supplied as an Authorization header carrying a bearer token (pn_...) or a team token created on the Parley site. No local runtime or packages are needed.
Installation
In SourceWeft
- Open Parley in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.weldra%2Fparley/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"parley": {
"type": "http",
"url": "https://parley.weldra.dev/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
