Connect Smokeball to your AI assistant
No catalog roulette. This page shows exactly where Smokeball stands as a hosted MCP connector, what legal tools you would get, and how writes stay guarded.
Every system here gets an honest, affirmative path: verified and instant, buildable and provisioned, human-assisted, or a done-for-you conversation. Zero dead ends.
Where Smokeball stands today
Matters, time entries, and documents: practice questions answered from the system your firm already trusts.
Also searched as smoke ball. The vendor's developer documentation lives at www.smokeball.com.
What a Smokeball connector would expose
The proposal you review during intake, separated into Read and Write. Nothing writes without asking you first.
Extracted from the vendor's API docs and human-reviewed before going live. Writes start one notch stricter.
- search_matters
Find matters by client, number, or status
- get_matter
Fetch one matter with key dates and contacts
- list_time_entries
List time entries by matter or user
- list_documents
List documents filed on a matter
- create_time_entryconfirm
Log a time entry on a matter
fields: matter, duration, description
- update_matter_statusconfirm
Change a matter's status or stage
fields: status
- add_matter_noteconfirm
Add a note to a matter
fields: body
- delete_time_entrydestructivedry-run
Permanently delete a time entry
fields: id
Every write asks first: it pauses on a preview of the exact change and runs only when you approve it, before anything reaches Smokeball. Turn off anything you never want your AI to touch.
From "Smokeball" to a working connector URL
Designed for operators, not developers. You never read API docs, manage tokens, or touch a line of code.
- 01
Name it
A 30-second eligibility check confirms your AI client accepts a custom connector URL, then you pick the software. This page pre-fills that step.
- 02
Describe what you need
Plain language, not configuration. What should the assistant be able to look up, and what should it be able to change?
- 03
Review your Connector Blueprint
The exact Read and Write tool list, before you pay anything. Every write ships on in confirm mode and asks before it runs, every tool is individually toggled, and anything destructive carries a distinct warning.
- 04
Deploy and paste the URL
You get a hosted connector URL plus paste-in instructions matched to your AI client, and a live test panel that confirms the connection.
Smokeball runs as a one-account connector
Smokeball supports a single credential, so the connector runs in Solo mode: it acts as one account and says so in plain language at auth time and in the dashboard. megamcp's own activity log still separates who did what by connection token.
You sign in to Smokeball and approve access. The connector requests the scopes its tool surface needs at connect time; every write still asks first, you can turn tools off at any time, and no password is ever shared.
Write access to Smokeball your IT team will approve
Nothing executes unapproved. Every write runs behind a human confirmation of the exact change, destructive actions demonstrate in dry-run until you graduate them, and any tool can be turned off.
Confirm mode
Enabled writes run through Multi Round-Trip Requests: the tool pauses, shows a human-readable preview of the exact change, and only proceeds with approval. Nothing reaches Smokeball on the model's intent alone.
Guardrails
Any tool can be turned off. Field-level constraints restrict what can be touched, per-tool rate limits are enforced at the gateway edge, and destructive operations ship in dry-run, demonstrating what they would do until you graduate them.
Activity log
Every tool call is logged: who, what, when, result. Write actions and confirmations are highlighted, redaction controls decide how much argument data is stored, and the log is append-only, with updates and deletes refused by the database.
Connecting Smokeball: the specifics
Can my AI assistant write to Smokeball?
Yes, once the assisted setup is done. The Smokeball API needs a person in the loop to map correctly; after that, writes follow the same rules as every megamcp connector: every write asks first and runs only when you approve it, and any tool can be turned off.
Is it safe to connect Smokeball to an AI assistant?
Safety is the architecture, not a setting. Every write asks first: it pauses on a human confirmation with the exact change previewed before it reaches Smokeball. Destructive operations demonstrate in dry-run and never execute until you graduate them, any tool can be turned off, and every call lands in an activity log with redaction controls.
If my team uses a Smokeball connector, whose name is on the actions?
Smokeball supports a single credential, so the connector runs in Solo mode and discloses it plainly: the connector acts as one account, stated at auth time and in the dashboard. megamcp's own activity log still preserves per-connection traceability, because every connection has its own token.
Which AI clients work with a Smokeball connector?
Any client that accepts a remote MCP connector URL: Claude (Free, Pro, Max, Team, and Enterprise), ChatGPT on paid plans with developer mode enabled, Cursor, and other MCP-compatible clients. Team and Enterprise workspaces may need an admin to allow custom connectors first.
How long until a Smokeball connector is live?
It depends on what the assisted setup involves, and you see honest timing the whole way: intake shows a build-queue position instead of a vague promise.
Anything specific to the Smokeball API worth knowing?
Yes. From our index notes on Smokeball: API access is partner-approved.
More Legal systems
Same category, same connector quality. Every one gets an honest verdict.
Connect Smokeball. We take it from there.
Start a 14-day free trial, no card: live reads plus 3 supervised writes, each executed only after you approve it.