How to Create a Sprint and Add Topics Using Content Hub MCP

Once Claude Desktop is connected to Infrasity's Content Hub via MCP, you can set up a full sprint, from creating it to populating it with topics to attaching published URLs, entirely from chat, without opening the dashboard.

Before you start, make sure Claude Desktop is connected to Content Hub via MCP (see the Content Hub MCP setup guide if you haven't done that yet).

Here's the flow.

Create a new sprint

Name the sprint and give it a start and end date, for example:

"can you add a new sprint in Infrasity org by the name of 'September 2nd half' which will start from 16th of September and end on the 30th of September"

Claude first resolves "Infrasity" to the org's actual company ID behind the scenes, since that's what the create call needs rather than a plain org name. It then creates the sprint and returns the result: September 2nd half, running Sep 16 to Sep 30, 2026, with a generated sprint ID like 21a90725-d227-4238-a414-94748f55b483. That ID is what every topic you add next gets attached to, so it's worth a glance even though you'll rarely need to type it yourself. Claude closes by prompting the natural next step: adding topics to it now.

Add topics to the sprint

Give Claude the title and target keyword for each topic you want added, for example:

"yes add a topic whose title would be '10 B2B Influencer Marketing Strategies That Reach Technical Buyers' and keyword would be 'B2B Influencer Marketing' and add another one whose title would be '11 YouTube B2B Marketing Best Practices for DevTool and SaaS Teams' and keyword would be 'YouTube B2B Marketing'"

Creating a topic requires a content_hub field, essentially which category or hub the piece belongs to, and if you haven't specified one, Claude asks rather than guessing silently, while still offering a sensible default ("Blog") so you're not blocked waiting on an answer. Both topics land in the sprint tagged with their titles and keywords, "10 B2B Influencer Marketing Strategies That Reach Technical Buyers" (keyword: B2B Influencer Marketing) and "11 YouTube B2B Marketing Best Practices for DevTool and SaaS Teams" (keyword: YouTube B2B Marketing), each starting out with a "planned" status: they exist in the sprint, but nothing about them is live yet.

Edit topic details

Once a topic is live, update it with a published URL by naming the topic and the URL, for example:

"okay add published url to both '[URL 1]' and '[URL 2]' respectively"

Claude updates both topics with their published_url field set, for example infrasity.com/blog/b2b-influencer-marketing-strategy-technical-buyers for the first one, but deliberately leaves the status untouched: attaching a URL and marking something published are two separate actions, so a topic can sit fully staged with its live link attached before you actually flip the switch. When you're ready, that's a second, explicit request:

"yes change the status to published"

Claude flips both topics from "planned" to "published" with their URLs attached, and offers the next logical field to fill in: published_date, the last piece that makes a topic's record fully accurate rather than just technically live.

The same three requests, create the sprint, add topics, update them as they go live, cover most of what a sprint needs day to day, so this is a flow worth reusing every time a new planning cycle starts rather than something you set up once.

Head to app.infrasity.com and check your own Sprints tab to see the sprint and topics you just created over chat.