Game night at eight?
Discord · connected clients
Versioned event + shared contextIdentity · roles · scope
Admission policy + entitlementsQueue · model · proposal
Durable work + provider adapterChannels · roles · rich messages
Scoped approval → typed dispatcherResult · recovery · run details
Durable receipts + redacted traceThe result, right where you asked.
Final answer before background traceA personality that fits your people. A forward deployment engineer to get it running with you, and a retainer to keep it working with you.
What would your server call yours?
Automated onboarding is in development.Pull up a chair. Follow a request through the machinery that makes a community feel effortless.
Keep exploringAsk from ChatGPT. Work in Claude or Cursor. Talk right in Discord. Alloy gives compatible clients a governed way to work with your community.
A browser-based MCP connection can make this happen without a coding client.
{name: "game-night"}MCP is the connection protocol. Alloy provides the tool and execution system; the AI client supplies its own model and context. Direct MCP calls enter Alloy's governed dispatcher without requiring a second conversational model loop. Discord conversations may use Alloy's configured provider path.
Client capabilities, plans and workspace settings determine which actions are available. Current ChatGPT help describes full custom MCP write support on Business, Enterprise and Edu web; Pro developer mode supports read/fetch. This differs from ChatGPT agent mode. Claude compatibility is a supported protocol path; final Alloy client acceptance must be demonstrated per release.
“Make a game-night channel.”
A simple sentence becomes a precise action. Scroll to see the checks, the tool call and the result fit together.
The client discovers the tool and supplies a channel name, type and topic. Alloy resolves the authorized context. Missing or ambiguous targets need clarification.
create_channelThe request has an actor, a server and a scope. Fresh Discord permissions and the connection grant both matter. Approval is tied to the actual proposed change.
scope → proposal → approvalDurable work, the canonical dispatcher and the Discord adapter carry the action. A model's suggestion does not bypass those controls.
queue → dispatcher → adapterThe completed action points to a returned Discord resource and a durable operation record. If a write has an uncertain outcome, Alloy must not blindly repeat it.
result → receipt → communityThe client asks which tools this connection can use.
{ "method": "tools/list" }Actual tool name and input fields. Fictional request, IDs and outcomes. Public summaries describe the work; they do not reveal hidden chain-of-thought.
Reliability is a set of behaviors you can inspect.
An expired or revoked grant cannot authorize another action. Reconnection must restore valid authority before work resumes.
Architecture behavior study · not a live fault injection or latency benchmarkClient/network latency, queue wait, provider generation and Discord response time are separate measurements. The release acceptance needs per-stage timings, denied-action tests, rate-limit behavior and restart evidence. A fast metadata endpoint is not proof of fast authenticated Discord operations. This proposal does not invent a p95 or uptime figure.
Channels, roles, messages, events, moderation and rich output. Inspect the real tool definitions behind the conversation.
Read the schema. No tool is executed here.
The inspected source contains 227 canonical tool definitions and 166 incoming MCP domain tools. Its Discord inventory accounts for 348 operations: 246 REST, 90 Gateway and 12 webhook. A listed operation is not automatically a callable tool; a tool can cover variants and each action still needs valid authority.
The baseline marks semantic parity as partially reviewed. This website study has not run live Discord or inspected production. The final release and client acceptance will be reconciled when the current MCP undertaking completes.
New ideas get a place to play. Your real community gets a release that has been checked, approved and observed.
The owner creates a private Discord server and a separate application. Alloy checks the guild binding, limited permissions and isolated stores before starting that Lab.
Source: schemas, adapters, permission rules, policy boundaries and regression fixtures.
Lab: startup isolation, read cohorts, an approved reversible write, cancellation and restart recovery.
Release: exact candidate, dependencies, resource envelope and retained recovery state.
Runtime: health, security, deep checks, one production gateway and an observed result.
Oracle: production TypeScript bot and private control plane. Current Trainer Labs target: A1, 1 OCPU / 6 GB.
Mac: source and development tools; the production-token gateway stays off. A separate Lab application is a different lane.
Website host: public site assets. It is not the bot VM. A customer deployment is sized and scoped in its own quote.
It identifies the candidate, checks, approved target and observed outcome. These are Alloy's release checks, not a third-party certification.
Source tests, Lab proof and Oracle production acceptance are distinct. A green earlier stage does not silently pass the next one.
Lab provisioning begins with a person creating the guild; automated onboarding is in development. Discord removed app-created servers in July 2025 ↗
Requests, approvals, connections and releases belong in one legible place. Here is the dashboard direction, using a fictional community.
Explore the tabs and run details. No runtime is connected and no changes leave this page. The real dashboard is a later implementation.
A Dungeons & Dragons server is a different world. Its Alloy can become the keeper of its characters, campaign lore and table rituals—with natural-language controls for the dungeon master.
Your party has a new member.
Bespoke installation conceptWe design the personality, tools, libraries and permissions with you. Dice mechanics, persistent character libraries and campaign controls would be built for this bespoke installation.
Start with what your community needs. Compare the features, the way you shape them, and the people who keep them working.
Commands are the beginning. Integrations, permissions, testing and ongoing changes give the build its shape.
Useful for a well-defined job. The next behavior needs its own design and implementation.
Published offers and estimates, reviewed 12 Sep 2026. Smaller commissions can cost less. Scope, revisions, hosting and maintenance differ; these figures establish the work involved, not a promised Alloy saving.
Make it a campaign companion, a community organizer, or a teammate with your own personality. Use natural language to coordinate its permitted Discord tools. We design the new behaviors with you, install the system, and stay involved as your community grows.
Every installation comes with a full maintenance retainer. Ask your Alloy first. When the work needs us, we're there.