Invompt MCP
by Invompt
README.md
<div align="center">
# Invompt MCP
<strong>Turn AI-host work into invoices you review before send.</strong>
<br />
Continue anonymously or OAuth via hosted MCP.
</div>
> **Prefer the hosted connector**
> Registry [`com.invompt/invompt`](https://glama.ai/mcp/connectors/com.invompt/invompt)
> -> [`https://mcp.invompt.com/mcp`](https://mcp.invompt.com/mcp)
> Continue anonymously | review-before-send | [www.invompt.com](https://www.invompt.com)
> Wellknown: [invompt-mcp](https://wellknown.network/agents/invompt-mcp)
> Local-beta/stdio in this repo is secondary.
<p align="center">
<a href="https://mcp.invompt.com/mcp">Hosted MCP endpoint</a>
|
<a href="packages/invompt-mcp/README.md">CLI reference (secondary)</a>
|
<a href="packages/mcp-core/README.md">MCP contract</a>
</p>
Prefer the hosted path above. This repo also ships a pre-1.0 local-beta CLI and
Guest stdio bridge for Claude Code or Codex (secondary).
## What it does
- Turns AI-host context into invoices you review before send.
- Lists and updates invoices and clients through the MCP contract.
- Hosted path: Continue anonymously or OAuth at mcp.invompt.com.
- Secondary local-beta: Guest stdio or hosted OAuth via this package (`invompt-local-beta`).
## Quick start
**Hosted (preferred):** Continue anonymously at
[`https://mcp.invompt.com/mcp`](https://mcp.invompt.com/mcp) (or OAuth), then review before send.
Cursor `mcp.json` (HTTP only - no headers / API key):
```json
{
"mcpServers": {
"invompt": {
"type": "http",
"url": "https://mcp.invompt.com/mcp"
}
}
}
```
**Local-beta (secondary):** `npx --yes invompt-mcp@next setup --host codex --mode oauth`
(replace `codex`/`oauth` with `claude-code`/`guest`). Restart the host, then review before send.
## Connection modes
| Mode | What it uses | Choose it when |
| --- | --- | --- |
| Hosted | HTTPS MCP endpoint | Default product path (Continue anonymously / OAuth). |
| Guest | Local stdio bridge | Local-beta pseudonymous credential (secondary). |
| OAuth | Hosted HTTPS via this CLI | Local-beta browser sign-in setup (secondary). |
The bridge does not open a listener or implement invoice business logic. It forwards
JSON-RPC only through the selected connection and rejects HTTP redirects.
## Security
Guest credentials are stored in the macOS Keychain by default. The optional file
fallback requires an explicit flag and uses restricted local permissions. The CLI
does not place credentials in a plugin manifest or host configuration, derive a
hardware fingerprint, or collect serial and MAC data. Never paste credentials,
tokens, or real invoice content into a public issue.
Report a vulnerability through [GitHub private vulnerability reporting][security-report].
[security-report]: https://github.com/Invompt/invompt-mcp/security/advisories/new
## Resources
- [CLI and onboarding reference](packages/invompt-mcp/README.md)
- [Transport-neutral MCP contract](packages/mcp-core/README.md)
- [Contract fixtures and service fake](packages/mcp-testkit/README.md)
- [Model Context Protocol documentation](https://modelcontextprotocol.io/)
- [Hosted Invompt MCP endpoint](https://mcp.invompt.com/mcp)
- [www.invompt.com](https://www.invompt.com)
## License
[MIT](LICENSE)
TDQS
B3.2/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap with other tools, making disambiguation perfect.
Naming Consistency5/5
A single tool inherently has consistent naming, as there are no other tools to compare it against for patterns or deviations.
Tool Count2/5
One tool is too few for a server named 'Invompt MCP', which suggests a broader invoicing domain; this feels thin and likely incomplete for typical invoicing workflows.
Completeness1/5
The server appears focused on invoicing, but with only a create_invoice tool, it lacks essential operations like retrieving, updating, listing, or deleting invoices, making it severely incomplete.
Maintenance
ActivityActive
ResponsivenessNo issues