# Ways to use Flung

> Page: https://docs.flung.dev/ways-to-use. Index of every page: https://docs.flung.dev/llms.txt

Flung is one service with several ways in: a plugin for Claude Code, an MCP server for every other agent, the REST API and its SDK for your own code, and webhooks to hear what happened. Pick by who is doing the work.

## TL;DR

| Question | Answer |
|---|---|
| I use Claude Code | Install the [Claude Code plugin](https://docs.flung.dev/claude-code-plugin.md): the server, four skills and a release hook, signed in with your browser. |
| I use another agent | Add the [MCP server](https://docs.flung.dev/mcp.md) to Cursor, VS Code, Claude Desktop, ChatGPT or Gemini. |
| I am writing code | Call the [REST API](https://docs.flung.dev/reference/api.md), or use the [TypeScript SDK](https://docs.flung.dev/reference/sdk.md) for typed calls with retries. |
| I need to know when a post goes out or fails | Add a [webhook](https://docs.flung.dev/webhooks.md). |
| Can I mix them? | Yes. They all work on the same workspace, accounts and posts: schedule from Claude Code, and hear the result on a webhook. |

## Side by side

| | Claude Code plugin | MCP server | REST API and SDK | Webhooks |
|---|---|---|---|---|
| Who does the work | Claude Code, for you | Your AI agent, for you | Your own code | Flung tells your code |
| Signs in with | Your browser (OAuth) | Your browser (OAuth), or an API key | An API key, or a connect token in a page | A signing secret per endpoint |
| Setup | Two commands in Claude Code | One address in your client | `npm install`, then a key | An address and the events to send |
| Adds | Skills for posting, connecting, release posts and status, and a hook after you tag | Every tool and workflow | Every endpoint, typed | Signed events, retried |
| Best for | Developers who post about what they ship | Posting and checking accounts from a chat | Products and scripts that post | Following up on what was published |

## Claude Code plugin

For Claude Code. The plugin is the MCP server with skills on top: Claude drafts a post per platform within its limit, passes your local time as you said it, and asks before it schedules anything. After a `git tag` or `gh release create` it offers to announce the release. [Install it](https://docs.flung.dev/claude-code-plugin.md).

```text
/plugin marketplace add flung-official/flung-claude-plugin
```

```text
/plugin install flung@flung
```

## MCP server

For every agent that speaks MCP: Cursor, VS Code, Claude Desktop and claude.ai, ChatGPT and Codex, Gemini, and Claude Code without the plugin. The agent signs in once in your browser and gets Flung's [tools and workflows](https://docs.flung.dev/mcp/tools.md); it gives you the platform's link to connect an account, and you approve there. [Connect an AI agent](https://docs.flung.dev/mcp.md) has each client's setup.

## REST API and SDK

For your own product or script. Every endpoint is in the [API reference](https://docs.flung.dev/reference/api.md); the [TypeScript SDK](https://docs.flung.dev/reference/sdk.md) has each one as a typed method, with retries and idempotency keys. To let your users connect their own accounts on your page, add the [connect panel](https://docs.flung.dev/connect-accounts.md). Start with the [Quick start](https://docs.flung.dev/quick-start.md).

```bash
npm install @flung.dev/sdk
```

## Webhooks

For hearing back. Flung sends a signed event to your endpoint when a post publishes or fails, when an account needs reconnecting, and more, and retries until your endpoint answers. Every way in above can schedule the post; a webhook tells your code what happened to it. See [Webhooks](https://docs.flung.dev/webhooks.md).

## See also

| Doc | Why |
|---|---|
| [Claude Code plugin](https://docs.flung.dev/claude-code-plugin.md) | Install, sign in, the skills and the release workflow |
| [Connect an AI agent](https://docs.flung.dev/mcp.md) | The MCP server in each client |
| [Authentication](https://docs.flung.dev/authentication.md) | API keys, OAuth and connect tokens |
| [Flung for AI agents](https://docs.flung.dev/agents/overview.md) | The order of calls and the rules, for an agent reading the docs |