Claude Abency connectorWhat Claude can do in your Abency account.
The Claude Abency connector lists 47 tools. 35 read brands, posts, SEO and ads data, 6 write (posts, media, keyword tracking), and 6 have no official description. Below: what Claude can run for your agency, what it can publish, and where the sources disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for an agency juggling many brands
Abency is built for marketing agencies and community managers who run several brands. With the connector, you ask Claude in plain English and it works across all of them from one connection: schedule social posts, look up Search Console data, research keywords and read ad performance, without opening each dashboard. Every brand stays isolated inside your own organization.
A week of posts in one request. Ask for three Instagram posts for next week: create_post creates and schedules each one, and list_posts shows what is already planned so nothing overlaps.
Quick SEO wins without exporting a spreadsheet. keywords_gsc_opportunities surfaces queries sitting between position 4 and 20 that already get impressions, the classic list of pages worth pushing.
A paid media check before the client call. meta_ads_overview sums up Facebook and Instagram Ads, and ads_compare sets the current period against the previous one.
What the directory sheet leaves out. Abency's own page describes WordPress, Brevo and Tag Manager tools that the sheet does not list, while the sheet shows six names, such as hours_summary, that Abency never describes. The SEO tools also depend on an Abency plan with the SEO module. And nothing runs by itself: Claude only calls these tools while it answers you, so a post goes out because you scheduled it, not because a trigger fired. Reacting to events in the background is the job of an automation tool, a different trade covered on the Integrations hub.
Five words before you connect
The vocabulary you will meet while plugging Abency into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs mid-answer, and the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, revocable later.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the chat.
- MCP
- The shared standard connectors are built on: the piece that lets an assistant like Claude talk to an outside service.
Connect Abency to Claude in three steps
- 01
Find Abency in Claude
In Claude's settings, open Customize, then Connectors, and look for Abency in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first, before any member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Abency in the window it opens; Abency says this route needs no token. If the link ever breaks, use Disconnect and connect again.
- 03
Read the authorization screen
Check the authorization screen before you approve access. It belongs to Abency, not to Claude, and it sets what the access covers. That access can also be withdrawn later from Abency.
The 47 tools, sorted by what they do
Abency gives Claude 47 tools: 35 that read your account, 6 that change something in it, and 6 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Tool names stay exactly as Claude shows them.
- 35 read
- 6 write
- 6 not documented
What Claude reads (35)
35 toolsThirty-five tools that look up brands, posts, SEO and ad data without changing anything.
ads_ad_groups
Lists the ad groups of a brand's campaigns together with their metrics, one level below the campaign view. Claude can then point to the group that drags the average down.
ads_ads
Shows the individual ads with their creative content, so Claude can read the actual headlines and texts running for a brand and compare them with the brief.
ads_campaigns
Returns a brand's campaigns with their metrics and status, the quickest way for Claude to see what is live, paused or ended, and how each one is doing.
ads_compare
Puts ad results for the chosen period next to the previous one, so Claude can tell you what improved and what slipped. Abency describes it simply as a comparison with the previous period.
ads_overview
Sums up advertising performance in one view: cost, clicks, CTR and ROAS. Campaigns, ad groups and individual ads each have their own tool for the detail.
ads_search_terms
Reveals the search terms that actually triggered the ads. Claude can scan that list for irrelevant queries that waste budget, or for new ideas worth their own ad group.
ads_timeseries
Delivers a day-by-day series of ad metrics, enough for Claude to spot a sudden drop, a spike or a recurring weekend pattern instead of a flat monthly total.
canva_export_design
Exports a design from the connected Canva account so it can be used in a post. Abency describes it as an export; no source says it alters the design itself.
canva_list_designs
Lists the designs available in the Canva account connected to the brand, so Claude can find the right visual by name instead of you browsing folders.
get_brand
Fetches the details of a single brand in your Abency organization, the context Claude needs before it works on that brand's posts, SEO or ads.
get_connections
Shows which social networks are connected for a brand. Abency supports Facebook, Instagram, LinkedIn, TikTok and YouTube, and each brand's connections are managed from its own panel.
get_post_status
Looks up the status of one post from its ID, so Claude can confirm whether it is scheduled, already published or still sitting as a draft.
gsc_keyword_positions
Returns the average Search Console position of specific keywords you name, rather than a broad list.
gsc_list_sites
Shows which Search Console property is configured for the brand, a check Claude can run before pulling any SEO figure, so the numbers come from the right site.
gsc_search_analytics
Pulls aggregated Search Console data for a brand: clicks, impressions and average position. Claude can then answer questions like which pages lost clicks this week.
gsc_top_queries
Fetches the top queries live from the Search Console API, as Abency puts it, for a brand's leading searches, rather than a list you would export by hand.
keywords_analyze_competitor
Compares a brand with a competitor domain and returns gaps and opportunities, the keywords where the rival shows up and the brand does not.
keywords_difficulty
Scores a list of keywords for difficulty on a 0 to 100 scale, so Claude can sort easy targets from long shots.
keywords_for_site
Reveals the keywords a domain already ranks for, whether that domain belongs to your client or to someone else entirely, such as a prospect or a rival.
keywords_generate_clusters
Groups a set of keywords into clusters using AI, which gives Claude a ready-made structure to turn a raw list into a content plan.
keywords_gsc_opportunities
Surfaces queries ranking between position 4 and 20 that already collect impressions. Those are the near-misses, where a small push on an existing page can lift a brand into the top results.
keywords_search
Runs a semantic search for keywords and attaches an opportunity score to each result, so Claude can rank ideas by meaning and potential, not only by exact wording.
keywords_search_volume
Gives the monthly search volume and its trend for the keywords you pass, so Claude can tell rising topics from fading ones before you commit time to them.
keywords_snapshots
Returns the history of daily snapshots for tracked keywords, enough for Claude to describe or chart how each position moved over time.
keywords_suggestions
Proposes related keywords starting from a seed term you give, a quick way to widen a topic list before deciding what to research further.
keywords_tracked_list
Returns every keyword under daily tracking, each with its latest position. From there, Claude can flag the ones that dropped since last week.
list_brands
Lists every brand your connection can reach. Abency says one connection covers all the brands of your organization, each kept separate from the others.
list_clients
Lists the organization's clients together with the brands linked to each one, so Claude can group work by client rather than by brand.
list_posts
Lists a brand's posts, with filters on status and date. That is where the existing calendar shows up, so you can see what is already planned before adding to it.
list_users
Lists the users of your Abency organization along with their role, useful whenever Claude needs to know who on the team does what.
meta_ads_campaigns
Returns Meta Ads campaigns with their metrics and objective, so Claude can judge each campaign against what it was set up to achieve.
meta_ads_compare
Compares Facebook and Instagram Ads results with the previous period, the Meta counterpart of the general ads comparison, so Claude can say what moved on Meta specifically.
meta_ads_overview
Summarizes Facebook and Instagram Ads performance for a brand in a single answer, before Claude looks at any campaign in detail.
meta_ads_structure
Opens one Meta campaign and lays out its ad sets, ads and creatives, so Claude can explain how the campaign is put together, level by level.
meta_ads_timeseries
Gives a daily series of Meta metrics such as reach, CPM and ROAS, so Claude can show trends and turning points rather than a single total for the period.
What Claude changes (6)
6 toolsSix tools that act on your Abency account. No source describes a confirmation of their own: the general rule further down applies.
create_post
Approval: see the ruleCreates a social post for a brand and schedules it. Abency says a post goes out at the date and time you give, and otherwise stays a draft until you confirm publication in another message.
delete_post
Approval: see the ruleCancels a post that was scheduled, so it never goes out. Abency's description stops at scheduled posts.
keywords_refresh_snapshots
Approval: see the ruleForces a fresh snapshot of tracked keyword positions instead of waiting for the daily one, so the figures Claude reads are up to date.
keywords_tracked_add
Approval: see the ruleAdds keywords to a brand's daily tracking, so their positions are recorded from now on.
update_post
Approval: see the ruleChanges an existing post: its text, its date or the platforms it goes to. Abency's example moves a post to another day and time.
upload_media
Approval: see the ruleUploads an image or a video to Abency so a post can use it.
Not documented (6)
6 toolsThe directory lists these six names and nothing else. No official text says what they do, so this page will not guess from a name.
get_work_order
This name appears in the directory's tool list and nowhere else: Abency's page, which describes its tools one by one, does not mention it. No source documents it.
hours_summary
Listed on the directory sheet, absent from the publisher's tool catalog and from Claude's help center. With no source describing it, this page leaves it at that rather than guessing from the name.
list_projects
A third name with no documentation at all. The publisher's categories (social, SEO, ads, web content, email, measurement, design, multi-brand) never include it, and no other official source covers it either.
list_tasks
Nothing official explains this one either: the sheet gives the name, Abency's page skips it. Treat it as an unknown, not as a feature you can count on.
list_time_entries
Fifth name in the undocumented group. No sentence from Abency or from Anthropic describes it, so this page does not say whether it reads or changes anything in your account.
list_work_orders
The last of the six names the directory shows without any description. Abency's documentation is silent on it, and this page will not fill that silence with an assumption.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account on your behalf. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked each time. They can also cap what a connector may do for the whole organization, for example keeping reads open and closing writes, and nobody overrides that from their own account. On Abency's side, the connection is tied to your organization, and Abency checks on every call that the requested brand belongs to it.
Which plans it works on
Out of 819 sheets in the official directory, not one shows availability by plan. That answer, connector by connector, is published nowhere: it is a real gap in the catalog.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can connect. Abency's own plans are a separate matter: they decide which Abency tools you can use. For this connector's current state in Claude, check its sheet in the directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing fires when a post underperforms or a keyword drops.
The tool list is an observed floor, not a promise: an admin can open actions that appear on no public sheet. The partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. This connector is documented only by its publisher; Claude's help center has no page for it. For a connector focused on email marketing, see the Claude activecampaign connector.
Which tools does the Abency connector really expose?
- Claude directory sheet ↗October 202647 named tools, including six that Abency never describes, and no WordPress, Brevo or Tag Manager tool.
- Abency's Claude page ↗October 2026Tools grouped by category, including web content on WordPress, email marketing on Brevo and measurement on Tag Manager, which the sheet does not list.
What this page followsThe two lists do not match, in both directions. This page follows the directory sheet, since that is what Claude receives when you connect. The final word belongs to your own account: check the connector's tool list in your Claude settings.
Need help connecting Abency to Claude?
A person reads every message.
