EzzyBills code-generation MCP server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
EzzyBills code-generation MCP server
This TypeScript MCP server supplies ChatGPT with the EzzyBills developer contract needed to generate standalone applications. It is a read-only knowledge service: it does not call EzzyBills, access customer data, or perform approval actions at runtime.
Architecture
ChatGPT
↓
get_ezzybills_developer_spec
↓
EzzyBills API catalogue, authentication contract, schemas, ID rules,
and generation rules
↓
Generated application
↓
EzzyBills REST APIsGenerated applications run independently of MCP. When they require EzzyBills access, they authenticate through the Developer Portal credentials:
CLIENT_ID + CLIENT_SECRET
↓
POST /oauth/token
↓
Authorization: Bearer <token>
↓
EzzyBills REST APIsThe client secret belongs only in a generated application's backend environment. It must never be embedded in browser or React code.
Related MCP server: LockSpec
MCP capabilities
The server exposes one MCP tool:
get_ezzybills_developer_specIt returns eleven structured sections:
coreArchitecture— actors and default stackauthContract— OAuth2 client-credentials, token lifecycleuniversalRules— rules for all generated applicationscontentSecurityRules— HTML sanitization, blob security, sandboxingactionRiskRules— READ_ONLY / WRITE / DESTRUCTIVE_OR_EXTERNAL classificationsapiCatalogue— 9 verified endpoints includinggetPurchaseOrders3workflowRecipes— step-by-step recipes for common tasksapplicationProfiles— optional UI blueprints (document-browser, approval-queue, etc.)idRules— parentDocumentId vs attachmentInvoiceIdspecificationGaps— items awaiting backend-developer verificationgenerationRules— flat compatibility alias
The server also exposes one MCP resource:
ezzybills://docs/developer-specThe resource serves docs/mcp_api_spec.md.
Requirements
Node.js 20 or newer
npm
The MCP server itself does not require EzzyBills account credentials.
Install and run
npm install
npm run devFor a compiled production-style run:
npm run build
npm startThe default endpoint is:
http://127.0.0.1:3000/mcpThe health endpoint is:
http://127.0.0.1:3000/Configuration
Variable | Default | Purpose |
|
| Network interface on which the HTTP server listens |
|
| HTTP port |
| local hostnames | Additional accepted HTTP Host header names |
| local hostnames | Additional accepted Origin header hostnames |
ALLOWED_HOSTS and ALLOWED_ORIGINS are comma-separated bare hostnames.
Do not include a URL scheme or port.
Example production configuration:
HOST=0.0.0.0
PORT=3000
ALLOWED_HOSTS=mcp.ezzybills.com,<azure-container-app-hostname>Configure ALLOWED_ORIGINS only when the connecting client sends an Origin
header. Add the hostname actually used by that client.
Host and Origin validation protect request routing; they are not user
authentication. If the developer specification is not intended to be public,
protect /mcp with the authentication or private-ingress arrangement chosen
for the deployment.
MCP Inspector
Start the server with
npm run dev.Select Streamable HTTP in MCP Inspector.
Connect to
http://127.0.0.1:3000/mcp.Confirm the single tool and resource listed above are available.
Docker
The multi-stage Dockerfile builds the TypeScript source, installs only production dependencies in the runtime image, and copies the Markdown specification required by the MCP resource.
docker build -t ezzybills-mcp .
docker run --rm -p 3000:3000 -e ALLOWED_HOSTS=localhost ezzybills-mcpFor Azure, set the production hostname in ALLOWED_HOSTS rather than using
the local Docker value.
Scripts
Command | Purpose |
| Start the TypeScript server |
| Type-check source and tests |
| Run the test suite |
| Compile |
| Run the compiled HTTP server |
| Type-check, test, and build |
Project layout
docs/mcp_api_spec.md
src/resources/ezzyBillsDeveloperResource.ts
src/tools/getEzzyBillsDeveloperSpec.ts
src/server.ts
src/httpConfig.ts
src/http.ts
test/developerSpec.test.ts
Dockerfile
.dockerignoreTestEzzyBillsMCP
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Connect ChatGPT or Claude to your CRM, store or shipping API. Keys stay out of the chat.
Connect QuickBooks, Xero, Bill.com, Blackbaud and Stripe to ChatGPT, Claude, Grok and any AI app.
Publish your API docs so AI assistants can look up endpoints and call your API correctly.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to search, browse, and generate example payloads from Sage Intacct REST API documentation using OpenAPI specs.98 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides AI coding agents with accurate OpenAPI contract details to prevent hallucinated API calls, supporting multi-version pinning, endpoint discovery, and request validation.42 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with generated REST APIs by discovering and using CRUD tools and read-only data resources.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding tools to discover platform capabilities, inspect authorized resources through fixed REST endpoints, and preview proposed JSON changes locally without applying them across EAP+OpenBPM, EXTN, and CloudFile.Apache 2.0