MCP servers that let an AI assistant do a company's everyday work.
Most are for services people use anywhere, such as Google Workspace, Notion, Bitwarden, Porkbun, Expo, the app stores and European banks; a second line is for companies in Romania, to file with ANAF, follow the trade register, invoice through Oblio and read the National Bank's rates.
Each server connects an MCP client, such as Claude Code, Claude Desktop, VS Code
or Cursor, to one service. They are built on one toolkit, so every tool says
what it can change: read (it changes nothing), write (it changes something
in your account) or money (it moves money, makes or unmakes a legal or fiscal
document, or commits you in a comparable way, such as a bank consent). Your
client asks you before each money call.
5 servers
For companies in Romania
The paperwork a company in Romania, and the people who run it, do online: e-invoices and declarations with ANAF, filings at the trade register, invoicing, and the National Bank's exchange rates. Each README ends with the other servers we found for that service, and what this one adds.
-
ANAF e-Factura
Read, check and file a Romanian company's e-invoices and e-Transport declarations with ANAF.
-
ANAF SPV
Download what ANAF posts to your SPV inbox, request documents, and validate or file declarations.
-
BNR exchange rates
Look up the National Bank of Romania's rate for any day, and convert amounts to and from RON.
-
Oblio
Issue and track a Romanian company's invoices on Oblio, with totals computed as ANAF checks them.
-
ONRC trade register
Follow your filings at Romania's trade register, with their documents, fee notes and invoices.
10 servers
For everyone
Servers for services people use anywhere. We built each one because the servers we found did less, or there were none; each README's last section names them and says what this one adds.
-
App Store and Google Play
Read and answer App Store and Google Play reviews, and see TestFlight feedback and crash logs.
-
Bitwarden
Give your assistant its own Bitwarden vault to create logins, type passwords and read 2FA codes.
-
Expo Application Services
Find out why an Expo build, workflow run or store submission failed, and roll out updates.
-
Enable Banking
Read, search and export statements and balances from banks across Europe, without moving money.
-
Google Workspace
Search and work in Gmail, Calendar, Drive, Docs, Sheets and Slides across several Google accounts.
-
Home Assistant
Read your Home Assistant's states, areas and history, and run its actions, approving locks first.
-
Notion
Search, read and write your Notion workspaces, with pages as Markdown and typed database queries.
-
Porkbun
Register domains and manage DNS, hosting and mail at Porkbun, with every purchase confirmed first.
-
Trademark search
Check whether a name is already a registered or pending trademark in the US or the EU.
-
TypeSafe
Get calibrated yes or no answers, choices and scores from TypeSafe's Jev, for one item or 1000 rows.
5 servers
Extras
These work, and we use them, but each is built for one particular setup or on an app's unofficial API, so they are not published to npm, the MCP Registry or as desktop bundles. Run them from a clone, and read the README first: it says what the server depends on and what can break.
-
Bolt Food receipts
Read your Bolt Food orders as itemised receipts matched to card charges, through an unofficial API.
-
Device broker
Share your own Android emulators, iOS simulators and desktops between AI agents, in fair turns.
-
Glovo receipts
Read your Glovo orders as itemised receipts matched to card charges, through an unofficial API.
-
Printer and scanner
Print, scan and check paper and toner on a network printer, with greys corrected for that printer.
-
Smart home
Press the buttons of a TV, heater or fan remote by name through a BroadLink IR blaster.
Quick start
You need Node 22.19 or newer and an MCP client. The trademark search needs no account and no key for US marks, which makes it a good first server:
git clone https://github.com/foreverworks/mcps.git && cd mcps
npm ci && npm run build
claude mcp add trademarks -- node "$PWD/servers/trademarks/dist/index.js"
Then ask your assistant: "Is Turnip already a registered trademark in the US for software?"
Every server's README has its install buttons, the commands for Claude Code and for clients configured with JSON, and the credentials it needs, step by step. A server starts and lists its tools before you configure anything; a tool that needs a credential you have not given answers with an error naming the variable to set. To run one copy that several clients share over HTTP, see docs/deploying.md.
#What every server does the same way
- Each tool says what it can change. Its class reaches your client in the
standard annotations (
readOnlyHint,destructiveHint), so a client can ask before a write. A server will not start with a tool left unclassified. - Money waits for you. A
moneytool asks your client to confirm every call; Claude Code does, whatever its permission mode. A deployment can instead have the server ask you itself, in one line naming the amount, the counterparty and the document (how). - A deployment can set a ceiling.
MCP_MAX_ACCESS=readturns a server into a read-only one, and a lower ceiling can be set per client. - Your data is not retyped. Files go in by path, never as text a model copies; amounts are exact decimal strings, never floating point; an unknown argument is refused by name; results report the SHA-256 of what was stored or sent.
- Every call leaves one audit line, without its arguments, its result or any token.
- It runs where you run it: over stdio, started by your client, or as one copy on loopback over Streamable HTTP, with a bearer token per client.
- Tests never touch a real account. Every outside dependency is a port with a fake, and the test environment has no credentials and no network.
Status
The servers are used every day by the people who wrote them. The servers for Romania and for everyone are not on npm yet: until the first release publishes them (to npm, the MCP Registry, and a Claude Desktop bundle for each), build them from source as above. The extras are never published.
Documentation
- Configuration: the variables every server shares, and the conventions for the rest.
- Deploying: client configuration, the HTTP transport, and running a server as a systemd service.
- Security: the threat model, the guard every call passes, money and confirmation, files in and out.
- Authentication: how clients, servers and the services behind them authenticate, and which options a deployment has.
- Architecture: how a server and the toolkit are built.
- Roadmap: what other MCP servers do that these do not yet, what is done, and what is still open.
- Releasing: how packages reach npm and the MCP Registry.