- Home
- Resources
- Integrations
- pg-aiguide
Claude pg-aiguide connectorWhat Claude can look up for you in the pg-aiguide library.
The Claude pg-aiguide connector exposes 2 tools: 2 read, 0 write, 0 left undocumented. One searches Postgres documentation, the other opens best-practice guides. Below: what each returns, what it never touches, who decides, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug the Claude pg-aiguide connector into your chats
Claude already writes SQL, but its idea of PostgreSQL can lag behind the current release. Tiger Data built pg-aiguide so a coding assistant checks the official manual and a set of opinionated guides before it answers. Plugged in, Claude quotes the version you run instead of memory.
Answers pinned to your Postgres version. Ask how a feature behaves and search_docs pulls the matching passages from the PostgreSQL manual, scoped by version, or from the Tiger Data and PostGIS documentation. You get the relevant excerpt, not a paraphrase from training data.
A schema reviewed against a written method. Before you design a table, view_skill opens one of Tiger Data's opinionated guides, which the publisher says cover schema design, data types, constraints, indexing, naming and performance tuning. Claude then reasons from that guide rather than from habit.
Now the part the directory sheet leaves out. No source describes this connector reaching your own database: it reads a shared library of documentation and guides, nothing of yours. TimescaleDB has both docs and skills, while PostGIS has docs only for now. And nothing runs by itself: Claude calls these tools while it answers, never on a schedule. For jobs that fire on an event, look at an automation platform from the Integrations hub, which does a different job.
Five words before you start
The vocabulary Claude uses around this connector.
- Connector
- A link you set up once between Claude and an outside service, so Claude can draw on it in the middle of a reply.
- Tool
- One named thing a connector lets Claude do. Claude picks the tools it needs on its own; the directory sheet lists them by name.
- Authorization
- The sign-in screen of the service itself, where a person grants the access Claude will use. Given once, and taken back the same way.
- Approval
- The confirmation Claude waits for before it changes something in an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service in one common way.
Add pg-aiguide to Claude in three steps
- 01
Find it in your settings
In Claude, open Customize, then Connectors, and look for pg-aiguide in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on for the organization before members can use it.
- 02
Start the connection
Hit Connect on its row. When a service asks you to sign in, it does so in its own window. If the link ever breaks, use Disconnect, then connect again from the same row.
- 03
Read what you approve
If an authorization screen appears, read it before you accept. It belongs to the service, not to Claude, and it sets what the access covers. Once done, the connector is ready in your next conversation.
The 2 tools, sorted by what they do
pg-aiguide gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Both tools consult a shared library. Names stay exactly as Claude shows them.
- 2 read
What Claude reads (2)
2 toolsTwo lookups in Tiger Data's documentation and guides, nothing tied to your data.
search_docs
Runs a search across three sources at once: the official PostgreSQL manual, scoped by version, Tiger Data's TimescaleDB documentation and the PostGIS manual. It mixes keyword matching with meaning-based matching, so a loosely worded question still lands on the right page.
view_skill
Hands Claude one of ten opinionated guides written by Tiger Data. The publisher describes them as PostgreSQL best practice on exploring schemas, schema design, indexing, data types, constraints, naming, performance tuning and recent PostgreSQL features. Claude reads the guide, then applies it to your question.
What Claude asks before acting
By default, Claude stops and asks before any action it takes on an account on someone's behalf. The request shows up in the chat at the moment it matters.
On Team and Enterprise, workspace owners decide whether members may let some actions through without being asked each time. They can also cap what a connector may do for the whole organization, keeping reading open and closing writing, and nobody overrides that from a personal account. Claude also works with the rights of the person connected and nothing more. Here, both tools only consult public documentation, and no source describes a confirmation step specific to either one.
Which plans include it
None of the 819 sheets in the official directory shows availability plan by plan. That answer is published nowhere, for this connector or any other.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner switches a connector on for the organization before members can connect. For the current state of pg-aiguide, check its own sheet in the directory from your account.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, and nothing starts on its own when a release ships or a schema changes.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's partner badge is not a security audit either, and Anthropic states on every sheet that it does not choose the tools a publisher exposes nor guarantee they behave as described. Only Tiger Data documents this connector: no Claude help article covers it, and the Claude connectors hub lists the others.
Need help connecting pg-aiguide to Claude?
A person reads every message.