Use STYD from Claude (MCP)

What it is

STYD answers business questions about your Odoo data and your PostgreSQL or MySQL databases. Once STYD is connected to Claude, you ask in plain language in Claude; STYD works out the answer from your data, with your own access, and sends it back to Claude together with how it was calculated.

STYD also answers from the documents and spreadsheets added to your workspace (Settings → Documents). Claude sees them as the “Uploaded files” connection, and an answer drawn from them lists its sources: the file and its page or section.

What you need

• A STYD workspace with prompts left (free prompts or a plan) and, to ask about your own company, at least one connection (Odoo, PostgreSQL or MySQL) — see “If you have not connected your data yet” below. A PostgreSQL or MySQL connection can answer as soon as STYD has read its structure: the AI Guide analysis and the owner’s edits improve the answers, but nothing has to be finished or confirmed first. An Odoo API-key connection works for every member with the API key’s Odoo user. On an Odoo connection through the STYD module, a workspace owner or admin first links your STYD account to your Odoo user.
• A role that can ask questions: owner, admin or member. Viewers can read in STYD but cannot ask questions, from Claude or anywhere else.
• AI apps allowed in the workspace. They are on by default; an owner or admin can turn them off (see Who controls it).
• A Claude plan (custom connectors work on Free, Pro, Max, Team and Enterprise; Free is limited to one custom connector). On Team and Enterprise, an Owner or Primary Owner (on Enterprise, also a custom role with library access) first adds the connector to the organisation, then each member connects it.

If you have not connected your data yet

You can add STYD to Claude first. If you have no STYD workspace yet, STYD creates one for you the first time Claude calls it, with the free prompts and the sample companies that come with a new account. If your STYD account has no data of its own yet, Claude tells you plainly that nothing is connected and where to connect it.

In the meantime you can try STYD on fictional sample companies: a DVD rental store and an airline (PostgreSQL), and an office-supply company (Odoo). STYD tells Claude to use a sample only if you agree, and to say that the data is fictional, not yours. A question on a sample uses a prompt like any other question.

• Odoo: open Connect Odoo. In Odoo, click your avatar, open your profile, then Account Security → New API Key (turn on developer mode if you do not see it). Create the key as the Odoo user whose data STYD should read — a dedicated read-only user is best: everyone in your workspace sees what that user sees. Odoo 15 or later; Odoo Online, Odoo.sh and on-premise. Help: Odoo connection.
• PostgreSQL or MySQL: open Connect a database and use a read-only database user. STYD uses an encrypted connection when your server offers one. Help: Read-only database users.
• Firewall and addresses: if your Odoo or database server only accepts known addresses, allow STYD’s addresses 109.123.235.222 (IPv4) and 2407:3640:2324:5796::1 (IPv6). STYD cannot reach a server that only has a localhost or private-network address: use its public address.
• What happens next: STYD reads the structure of a database. Your first AI Guide analysis is included while your workspace still has a setup left (see Pricing) and starts by itself; otherwise an owner or admin sees its price and confirms it. You can already ask questions before the analysis is done. Odoo needs no analysis, and STYD takes you to your first Business Checkup, which starts by itself. Sign in to STYD with the same email you used to connect Claude.

How to connect

1. In Claude, add STYD. Open STYD's listing in the Claude directory and add it from there — or open Settings → Connectors, choose Add custom connector, give it a name (for example “STYD”) and paste the address above. Then choose Connect.
2. Sign in to STYD. A STYD page opens in your browser. If you are not signed in, you see the page “Continue to Speak To Your Database”: continue with Google, or enter your email address and open the sign-in link STYD sends you. If you are already signed in, STYD goes straight to the next step.
3. Approve. STYD asks “Allow “Claude” to use your STYD account?”. The page shows the app's name (declared by the app itself), the address you will be sent back to, what the app will be able to do — read data you already have access to, read-only, ask questions that use the prompts of the workspace they are about, in every workspace you belong to, including ones you join later — and the STYD account you are signed in with. Check the account, then choose Allow. Deny cancels.
4. Back in Claude. You return to Claude and the connector shows as connected. Ask your question in a conversation where the STYD connector is turned on.

If something goes wrong

• “This request has expired” or “This request is not valid”: go back to Claude and connect again.
• Signed in with the wrong account: sign out of STYD, sign in with the right account, then connect again from Claude.
• “Not available yet”: connecting AI apps is not open for your account yet. Contact us if you need it.

What Claude can do

STYD gives Claude five tools. All of them only read.

List workspaces list_workspaces

Lists the STYD workspaces you belong to, your role in each, whether AI apps are allowed there and how many prompts are left.

List connections list_connections

Lists the Odoo, PostgreSQL and MySQL connections you can ask about, and the Uploaded files connection that holds your documents, each with its workspace and whether it is ready.

Describe available data describe_available_data

Shows what one connection can answer: on Odoo, the business areas you can read and example questions; on PostgreSQL or MySQL, the tables you can ask about, their descriptions and the owner's business terms; it also lists your uploaded documents by name.

Ask a question ask_question

Sends one question to STYD and returns the answer with how it was calculated; for a follow-up, Claude is told to pass back the conversation identifier that ends every answer, and without it STYD starts a new conversation.

Get an answer get_answer

Fetches an answer that took longer than about 45 seconds to compute.

Example questions

Cost

Each answer costs one prompt from the workspace the question is about — whatever the answer says, including an answer that the data does not hold, a request to be more specific, or a refusal. Each answer tells Claude how many prompts it used. These are the same prompts as in STYD's own chat; you can follow usage in Settings → Usage.

Free

• Listing workspaces and data sources, describing what can be asked, and fetching an answer that is still being computed.
• A question STYD does not run — for example because the workspace has no prompts left, AI apps are turned off there, your role cannot ask, or too many questions were sent at once.
• A question that fails with an error.
• On Odoo: a reply that reports an error or that Odoo could not be reached, that Odoo questions are turned off for the connection, or (on an Odoo connection through the STYD module) that your account is not linked to an Odoo user yet — and a reply given while STYD's Odoo question service was temporarily unavailable.

When the prompts run out

If the workspace has no prompts left, STYD does not run the question, tells Claude so, and no prompt is used. A workspace owner can add prompts from STYD: top-up prompts at any time, or a plan (see Pricing).

Limits and safety

• Read-only. Database questions run inside a read-only transaction, and STYD calls only read methods in Odoo. STYD never changes your data.
• Answers never mix workspaces. Each question is about one connection in one workspace, every result names its workspace, and the prompt comes from that workspace. If you belong to several workspaces, Claude sees them as separate.
• You see what you can see in STYD. Claude acts as you, with your role and your own access. On an Odoo connection through the STYD module, STYD limits you to your linked Odoo user's access rights (accounting, sales, purchase, inventory) and companies, not every Odoo record rule; on a connection set up with an Odoo API key, you see what that key's Odoo user may read. On PostgreSQL and MySQL, tables an owner or admin has hidden from you are left out. Claude can open only your own STYD conversations, never another member's.
• Always hidden: passwords, tokens, keys, and card or bank numbers. Names, email addresses and phone numbers are not hidden. Long lists are cut to 50 rows.
• Size and speed: a question can be up to 1,000 characters. A table in an answer shows up to 50 rows, 12 columns and 200 characters per cell, and a whole answer is cut at 32 KB (the answer says when a table is truncated). Describing a connection lists its first 60 tables. Asking waits about 45 seconds; for a longer answer Claude asks again, and each try waits up to 20 more seconds. An app can make about 300 requests per minute; beyond that STYD asks it to wait.
• Documents: Claude can only ask about files already added in STYD; it cannot upload, change or delete a file.
• Rate limits: up to 30 questions per minute per person in each workspace, and at most 8 questions waiting per person and 20 per workspace. Beyond that, STYD asks you to wait a moment and try again; nothing is charged.
• Data stays data. Values in an answer come from your records; Claude is told to treat them as data, never as instructions.

Who controls it

Workspace owners and admins

• Turn AI apps off or on: Settings → AI apps → Workspace setting → “Allow AI apps in this workspace”. When it is off, AI apps get a message that AI apps are turned off for this workspace and nothing is run, including calls made with a workspace API key. STYD's own chat is not affected.
• See who connected: Settings → AI apps → “Members' connected apps” lists each member who connected an AI app, the app's name, the address it returns to, when it was connected and when it was last used in this workspace. The list is read-only: each member disconnects their own apps. Removing a member from the workspace also ends their access to it from Claude.

Each user

• In Claude: open Settings → Connectors and disconnect or remove the STYD connector.
• In STYD: Settings → AI apps → “Your connected apps” → Disconnect, then confirm. The app loses access immediately. Only you see this list.
• Do both to be sure the connection is closed on each side. A connection that is not used for 30 days ends on its own, and every connection ends after 90 days; Claude then asks you to connect again.

Privacy and support

Questions you ask from Claude, and STYD's answers, are kept in your STYD conversation history like questions asked in STYD, marked with the app's name (for example “via Claude”). Read the Privacy Policy and the Terms of Service.

Need help? Use the support page or email contact@speaktoyourdatabase.com.