MCP: use STYD from AI apps

Version française

Use STYD from Claude (MCP)

Add Speak To Your Database (STYD) to Claude from Claude's directory or as a custom connector, then ask business questions about your company's data without leaving your Claude conversation.

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.

Read-only. STYD only reads your data. It cannot create, change or delete anything in Odoo or in your databases.

What you need

  • A STYD workspace with prompts left (free prompts or a plan) and at least one connection (Odoo, PostgreSQL or MySQL). A PostgreSQL or MySQL connection is ready to answer once its Data Guide has run. On Odoo, a workspace owner or admin may first need to link 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 that allows custom connectors.

How to connect

Connector addresshttps://speaktoyourdatabase.com/mcp
  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, and whether AI apps are allowed there.
List connections list_connections
Lists the Odoo, PostgreSQL and MySQL connections you can ask about, 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.
Ask a question ask_question
Sends one question to STYD and returns the answer with how it was calculated; a follow-up in the same Claude conversation continues the same STYD conversation.
Get an answer get_answer
Fetches an answer that took longer than about 45 seconds to compute.

Example questions

Odoo

  • “What was our revenue last month?”
  • “Which customers have overdue invoices, and how much do they owe?”

PostgreSQL or MySQL

  • “Who were our top 5 customers by total spend last year?”

The PostgreSQL or MySQL example fits a music store's sales database (customers, invoices, tracks); ask about your own tables in your own words. Put the period, customer, product or status in the question. Answers come in the language of the question.

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 that your account is not linked to an Odoo user yet — and a reply given while STYD's Odoo question service was temporarily unavailable.

Limits and safety

  • Read-only. Database questions run in read-only mode, and Odoo is only read. 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 Odoo, you see only what your linked Odoo user may read (on a connection set up with an Odoo API key, 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. Long lists are cut to 50 rows.
  • 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 (MCP)”. When it is off, AI apps get a message that AI apps are turned off for this workspace and nothing is run. 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.