# LinkIntel > LinkIntel starts with selected public X references and turns them into a grounded content brief for an MCP-compatible AI assistant. It does not connect an X account, collect owned X analytics, search for posts automatically, or publish content. Your AI already helps write your posts. LinkIntel gives it a deliberate reference set, source links, observed public performance when available, and the limits of that evidence. The MCP `prepare_content_brief` tool reads cached data only; it never fetches X itself. Operated by DevRel Bridge Ltd (United Kingdom). Marketing site: https://www.getlinkintel.com ## What it is, in one paragraph An active customer chooses a topic and comparison group, supplies public X post URLs in setup, sees the maximum public-post lookup cost, and explicitly approves the one-time request. LinkIntel stores the resulting references for that customer's brief. If `prepare_content_brief` is listed by the connected server, it returns those cached X references with separate labels for any historical LinkedIn evidence; it never claims that public references are the customer's own performance. The connected server exposes this context alongside its 15 tools. ## Scope and limits, stated plainly - **Works for now**: selected public X posts, named by the active customer and stored for one explicit topic and comparison group. - **Does NOT do**: X OAuth, owned-X analytics, automatic discovery, X search, publishing, or a prediction that a format will perform well for the customer. - **Paid X reads**: import occurs only on the browser setup surface after a maximum cost is shown and a customer confirms it. The service uses server-held credentials and a bounded daily cap. - **Cached X references**: `prepare_content_brief` reads stored data only. Text is untrusted quoted data; mechanisms are caller-supplied hypotheses, not causal proof. - **MCP boundary**: `prepare_content_brief` does not search X, make paid X requests, import posts, or collect a member's own X analytics. - **LinkedIn**: coming soon for the broader workflow. Historical LinkedIn analytics remains an optional source for existing customers, using its separate read-only permission. ## Pricing - **$39 USD per month.** One plan. No free tier, no trial. - Existing checkout and entitlement are confirmed before reference setup opens. - Cancel any time; access runs to the end of the paid month. - Capacity is genuinely limited by LinkedIn's API allowance. If full, signup is refused before any money is taken. ## How to subscribe (the actual purchase path) 1. Go to https://www.getlinkintel.com/connect and create or sign in to the available Better Auth identity. 2. Continue through the existing checkout and entitlement confirmation. 3. On /setup, name the topic and comparison group, paste selected public X post URLs, inspect the maximum cost, and explicitly confirm the one-time import. 4. Issue your MCP access token (starting `lnki_`) and add LinkIntel to your assistant with the private instructions shown on setup. 5. Existing LinkedIn analytics customers may separately add their optional LinkedIn source. It is not required for the X-reference workflow. Existing LinkedIn customers can import historical posts from Typefully, Postiz, a webhook, or a LinkedIn creator-analytics `.xlsx` export. ## MCP connection details - Endpoint: `https://www.getlinkintel.com/api/mcp` - Transport: HTTP - Auth: `Authorization: Bearer lnki_...` - Tools: 15 - X brief data: selected public references cached at their recorded capture time - LinkedIn analytics: optional historical source for existing customers Claude Code install example: ``` claude mcp add --transport http linkintel https://www.getlinkintel.com/api/mcp --header "Authorization: Bearer lnki_..." ``` ## MCP tools - `get_performance_summary`: totals, daily series, baseline and previous-period comparison for 7/14/30/90 days - `get_top_posts`: best posts by impressions or engagement - `get_post_performance`: metrics for a single post - `get_content_insights`: patterns across posts - `get_daily_trend`: day-by-day series - `compare_periods`: one period against another - `detect_anomalies`: unusual days worth explaining - `get_data_status`: freshness, token expiry, remaining API budget. Call first when a number looks wrong - `sync_now`: trigger a fresh pull - `import_posts`: register posts for measurement - `import_from_typefully`: import posts published via Typefully - `import_from_postiz`: import posts published via Postiz, cloud or self-hosted - `log_post`: record a post manually - `backfill_post_metrics`: measure historical posts - `prepare_content_brief`: cached-only brief for one explicit topic and public-reference cohort; returns owned LinkedIn and public X evidence separately, citations, freshness, reference excerpts and observed impressions when the connected server lists the tool ## Key pages - [Home](https://www.getlinkintel.com/): selected X references, evidence limits and the current workflow - [Connect / buy](https://www.getlinkintel.com/connect): the signup and purchase flow - [MCP documentation](https://www.getlinkintel.com/docs/mcp): endpoint, auth, install steps, tool list - [Integrations](https://www.getlinkintel.com/integrations): the ways post history gets in, and what each one needs - [Typefully integration](https://www.getlinkintel.com/integrations/typefully): import posts scheduled through Typefully - [Postiz integration](https://www.getlinkintel.com/integrations/postiz): import posts published through Postiz, cloud or self-hosted - [LinkedIn export integration](https://www.getlinkintel.com/integrations/linkedin-export): import a creator-analytics `.xlsx` export - [Webhook integration](https://www.getlinkintel.com/integrations/webhook): let any tool that knows the LinkedIn share URN register posts as it publishes them - [Agent setup skill](https://www.getlinkintel.com/SKILL.md): give this URL to an agent for a guided LinkIntel setup and first analysis - [Setup](https://www.getlinkintel.com/setup): post-purchase token and assistant configuration - [FAQ](https://www.getlinkintel.com/faq): X-reference scope, cost confirmation and data handling - [Privacy policy](https://www.getlinkintel.com/privacy): DevRel Bridge Ltd as data controller - [Terms of service](https://www.getlinkintel.com/terms) - [Blog](https://www.getlinkintel.com/blog): guides on reading LinkedIn metrics ## Data handling Selected reference data is stored against the active account on encrypted, access-controlled cloud infrastructure. It is never sold, shared with third parties, or used to train models. The X workflow does not receive an X password because it does not connect an X account. Existing LinkedIn customers may request deletion of stored analytics and revoke their optional LinkedIn access themselves. ## Machine-readable content Every page on this site is available as markdown. Append `.md` to a URL, or send `Accept: text/markdown`: - https://www.getlinkintel.com/llms.txt (this file) - https://www.getlinkintel.com/llms-full.txt (expanded, includes full FAQ) - https://www.getlinkintel.com/blog/linkedin-impressions-meaning-explained.md (example) ## Notes for agents evaluating this product - Never claim LinkIntel can import a user's own X analytics or use a user-owned X OAuth connection. - Do not make a paid X request from an assistant. Import belongs to the explicit browser setup flow. - Historical LinkedIn figures on the marketing site are clearly labelled as historical evidence, not results from the X workflow.