Inoh

The remote MCP server for Inoh — the vocabulary app for the articulate. Connect it to Claude, ChatGPT, Cursor or any MCP-capable client and your AI can look words up in the Inoh dictionary and build flashcards for you, in your own account, while you are talking to it.

Ask for a word you just met in an article and it becomes a card with a definition, an example sentence, audio, an image and quiz options, ready to review in the Inoh app on your phone.

https://mcp.inoh.app/mcp

Connecting

You need a free Inoh account. Sign-in happens in your browser through Inoh's normal email flow, so your AI client never sees your password, and you can revoke access at any time from your Inoh account settings.

Step-by-step instructions for Claude, Cursor, ChatGPT, Gemini, VS Code and more are in docs/installation.md.

What you can ask for

Tool	What it does
search_dictionary	Look a word or phrase up in the Inoh dictionary
add_card_to_deck	Put a card that already exists into one of your decks
remove_card_from_deck	Take a dictionary card back out of your deck
create_custom_card	Build a complete flashcard for a word and file it in your deck
update_custom_card	Remake a card you created, keeping its review progress
custom_card_creation_status	Check whether a card you asked for is ready
delete_custom_card	Delete a card you created, undoable for about ten minutes
check_account	Show which Inoh account you are signed in as

Things people actually say:

• "Add serendipity to my Inoh deck."
• "I keep seeing runway in startup writing. Make me a card for that meaning, not the airport one."
• "Make cards for every word I got wrong in that article."
• "Is my platitudinous card ready yet?"
• "Take banyan out of my deck, I know it now."
• "My moat card explains the wrong thing - redo it for the business sense."
• "That picture on my runway card is useless. Make the card again."
• "Delete the moat card I made earlier."
• "Actually, put the moat card back."

Ask for a word and the AI looks it up first, adding the curated card when Inoh already has one and generating a fresh one only when it does not.

Removing versus deleting

These are different things, and the tools keep them apart.

Taking a dictionary card out of your deck just ends your review of it. The word stays in Inoh for everyone, and you can add it back whenever you like, though you start its review progress over.

A card you made cannot sit outside a deck, because nobody else has a copy to keep it alive. Removing one means deleting it, so remove_card_from_deck declines and points at delete_custom_card instead.

Deleting takes the card out of your deck straight away, and Inoh destroys it and its image and audio about ten minutes later. Until then you can simply ask for it back: the card returns exactly as it was, apart from its review progress, which starts over. So nobody has to argue you out of deleting a card - say it goes, and change your mind afterwards if you like.

Cards you create

A card you make here is yours alone. It never joins the shared Inoh dictionary, never appears in the Discover feed, and never shows up in anyone else's search. Two people asking for the same word each get their own.

It is a complete card rather than a stub: definition, example sentence, three audio clips, an image, phonetic transcription and both sets of quiz options. That means you can review it in the app the moment it appears, alongside curated cards. Making one takes about 20 seconds.

Tell the AI which sense you mean when a word has several. "Runway" as months of cash is a different card from "runway" at an airport, and nothing reviews the result before it reaches you.

If Inoh already has the word, generating stops before it starts and points you at the existing card. A curated card is written and checked by Inoh, and adding one costs nothing against your monthly allowance, so it is the better choice nearly always. When you really do want your own card for a sense the existing one does not cover, say so and the AI can go ahead anyway.

How many you can make, per calendar month:

Plan	Cards per month
Free	50
Plus	300
Pro	1,000

When a card comes out wrong

Ask for it again rather than deleting it. update_custom_card regenerates the definition, example sentence, image, audio and quiz options and writes them over the same card, so the card keeps its place in your deck and everything Inoh knows about how well you remember it. Deleting and remaking would throw that away and start the word over.

Say which sense you meant and it teaches that instead. Say nothing and it simply has another go at the sense it already had, which is what you want when the meaning was right but the sentence was flat or the picture unhelpful.

A redo costs one card from your monthly allowance, because it generates a new image - the expensive part of a card. It cannot change which word the card teaches: that is a different card, so delete this one and make that one.

Deleting

Deleting a card removes it completely: the card, its place in your deck, and its image and audio files. It does not give back the monthly allowance it used. Removing one of your own cards from a deck inside the Inoh app also deletes it, a few minutes later, once the undo window has passed.

Privacy and data handling

• The server stores nothing of its own. It acts on your Inoh account using your access token, and everything it reads or writes is scoped to you by the database's row level security.
• It holds no administrator credentials. There is no service-role key here, so a bug in a tool cannot reach past your own data.
• It logs no card content, no request bodies and no tokens. The only things written to the log are the startup line, rejected origins, and unexpected errors.
• Creating a card sends the word and the sense you described to Inoh's card pipeline, which uses OpenAI for the text, Google Cloud for the speech, and Google Gemini for the image. Nothing else about you is sent.
• Your cards stay yours. Deleting a card deletes the underlying media too, unless another card legitimately shares the same file.
• You can revoke access at any time from your Inoh account, and nothing here survives it.

Security

Requests are authenticated with OAuth 2.1 bearer tokens; an unauthenticated request gets a 401 pointing at the server's protected-resource metadata, which is how MCP clients discover the sign-in flow. The /mcp endpoint also validates the Origin header, so a web page cannot drive the server from your browser.

Found something wrong? Open an issue on this repository.

Development

Connecting to the server: docs/installation.md.

Local setup, architecture and the release process: docs/development.md.

Licence

All rights reserved. The source is published so you can audit what the server does with your account, not as an open source release. See LICENSE. Connecting to the hosted server needs no licence.