mcp-bluesky-brand-presence-mapper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token. Get it at https://console.apify.com/account/integrations. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| map_bluesky_brand_presenceA | Resolve a company domain, or a Bluesky handle, to that company's official Bluesky account through the public AT Protocol API. Returns the profile URL, handle, DID, exact follower, following and post counts, display name, bio and account creation date, as one flat Clay ready row. Counts are EXACT here, not rounded, unlike every other platform in this family. When the resolved handle IS the company domain, Bluesky granted it after a DNS check the company had to pass, and the row flags that as the strongest identity evidence available. A company with no Bluesky account returns not_found, which is a real and common answer. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another tool in this server. Its purpose is singular and clearly stated.
The sole tool uses a clear snake_case verb_noun pattern: map_bluesky_brand_presence. With only one tool, there are no naming conflicts or inconsistencies to evaluate.
A single tool is slightly thin for a server, but it is appropriately scoped for the specific operation of mapping one Bluesky brand account. It does not feel bloated or arbitrary.
The tool covers the core resolution and profile-metrics use case, including exact counts, identity evidence, and a not_found response. Minor gaps exist, such as batch lookups or broader brand-search operations, which agents would need to work around with repeated calls.