Integration

SourceForge integration

SourceForge (the Allura platform) hosts open source projects. Read a project's metadata and tools, read and edit wiki pages, search, read, create and update tracker tickets and reply on their discussions, browse discussion forums and threads, read and post blog entries, manage repository push webhooks, and read user profiles. Tools are addressed by their mount point in the project (often wiki, tickets, discussion, blog). Project creation, export and tool installation or arrangement are left out. Reads of public projects work anonymously; actions use a bearer token from the SourceForge OAuth page in the Authorization header.

Connect SourceForge How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SourceForge.Built from the 30 SourceForge tools below, on the connection you add once.

What you can do with SourceForge

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

P, 15 operations

create_blog_postCreate blog postPOSTCreates a blog post with a title, Markdown text, labels and state (draft or published).
get_blog_postGet blog postGETReturns one blog post: title, author, Markdown text, labels, state and discussion. year, month and title come from the post URL in list_blog_posts.
get_external_linkGet external linkGETReturns the URL an external link tool points to.
get_projectGet projectGETReturns a project: name, summary, description, members, categories and its installed tools with their mount points (pass a mount point as wiki, tracker, discussion, blog, link or scm_tool to the other tools).
get_repositoryGet repositoryGETReturns a code repository tool (Git, SVN or Mercurial): name, commit count and clone URLs.
get_ticketGet ticketGETReturns one ticket by number: summary, description, status, reporter, assignee, labels, custom fields, attachments and its discussion thread with posts.
get_wiki_pageGet wiki pageGETReturns one wiki page by title: Markdown text, labels, attachments, last modification date and its discussion posts.
list_blog_postsList blog postsGETLists the posts of a blog tool with their title and API URL. The URL ends in year/month/title, the values get_blog_post takes.
list_forumsList forumsGETLists the forums of a discussion tool with their name, description, topic count and last post.
list_forum_topicsList forum topicsGETLists the topics of a forum (forum shortname from list_forums) with subject, replies, views and last post.
list_ticketsList ticketsGETLists the tickets of a tracker tool (ticket number and summary), with the tracker configuration, milestones and saved searches. Page with page and limit.
list_wiki_pagesList wiki pagesGETLists the titles of every page of a wiki tool. Pass a title to get_wiki_page.
save_wiki_pageSave wiki pagePOSTCreates the wiki page with this title, or replaces its text and labels if it exists. Requires a token with write access to the project.
update_blog_postUpdate blog postPOSTUpdates a blog post. Send only the fields to change; leave a field out to keep its current value.
update_external_linkUpdate external linkPOSTChanges the URL an external link tool points to. Requires admin access to the project.

Webhook, 5 operations

create_webhookCreate webhookPOSTCreates a repo-push webhook on a repository tool: SourceForge calls url after each push. Requires admin access to the project.
delete_webhookDelete webhookDELETEDeletes a repo-push webhook by id, as listed by list_webhooks.
get_webhookGet webhookGETReturns one webhook of a repository tool by id, as listed by list_webhooks.
list_webhooksList webhooksGETLists the repo-push webhooks of a repository tool. Requires admin access to the project.
update_webhookUpdate webhookPOSTChanges the URL (and optionally the secret) of a repo-push webhook.

Thread, 3 operations

get_forum_threadGet forum threadGETReturns the posts of a forum topic (thread id from list_forum_topics) with author, text and timestamp.
get_ticket_commentGet ticket commentGETReturns one post of a ticket discussion thread by its slug, as listed in get_ticket_thread.
get_ticket_threadGet ticket threadGETReturns a ticket discussion thread and its posts. The thread id is the last part of the ticket discussion_thread_url, or discussion_thread._id in get_ticket.

New, 2 operations

create_ticketCreate ticketPOSTCreates a ticket in a tracker. Requires ticket_form.summary; other fields default. Needs a token allowed to create tickets. Answers with a redirect, not the ticket: find the new ticket with list_tickets or search_tickets.
create_ticket_commentCreate ticket commentPOSTAdds a comment (a new post) to a ticket discussion thread.

Profile, 1 operation

get_user_profileGet user profileGETReturns a user profile: name, join date, location, web pages, skills, social networks and the projects the user belongs to.

Reply, 1 operation

reply_to_ticket_commentReply to ticket commentPOSTReplies to one post of a ticket discussion thread, identified by its slug.

Save, 1 operation

update_ticketUpdate ticketPOSTUpdates a ticket by number. Fields left out keep their value, except ticket_form.labels: leaving it out removes every label, so resend the current labels from get_ticket. Answers with a redirect, not the ticket.

Search, 1 operation

search_ticketsSearch ticketsGETSearches a tracker with a query (for example status:open or labels:bug) and returns the matching tickets with all their fields.

U, 1 operation

get_user_projectGet user projectGETReturns the personal project of a user (u/username): summary, tools such as personal Git repositories, members and profile API URL.

Use SourceForge from Claude Code, Cursor or Codex

Connect SourceForge in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SourceForge operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SourceForge

Create your workspace
Sign up free. Nothing to install.
Connect SourceForge once
Add your SourceForge connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.