Post For Me

MCP数据服务

提供方 DayMoonDevelopment

数据服务 未标注 API Key 社区 / 第三方 CursorVS CodeCodexZed

Quickly integrate social media platforms directly into your product to power posting, feeds, analytics, and more through a single, simple API.

一句话选型结论

按资料字段整理

Post For Me 属于数据服务类 MCP 服务器,传输方式未标注,API Key,可直接接入 Cursor、VS Code、Codex 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

social media posting analytics feeds tiktok x twitter facebook

支持客户端

适用场景

social mediapostinganalytics

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Cursor、VS Code、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、VS Code 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Post For Me当前 未标注 未标注 未标注 无 未标注
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方DayMoonDevelopment上游标注的维护方 DayMoonDevelopment
分类数据服务本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

11.3 KB
来自项目仓库与上游目录的原文,未做删改

Post For Me TypeScript API Library

>)

This library provides convenient access to the Post For Me REST API from server-side TypeScript or JavaScript.

The REST API documentation can be found on api.postforme.dev. The full API of this library can be found in api.md.

It is generated with Stainless.

MCP Server

Use the Post For Me MCP Server to enable AI assistants to interact with this API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.

> Note: You may need to set environment variables in your MCP client.

Installation```sh

npm install post-for-me


## Usage

The full API of this library can be found in api.md.```js
import PostForMe from 'post-for-me';

const client = new PostForMe({
  apiKey: process.env['POST_FOR_ME_API_KEY'], // This is the default and can be omitted
});

const socialPost = await client.socialPosts.create({
  caption: 'My first post!',
  social_accounts: ['sa_1234'],
  media: [{ url: 'https://picsum.photos/1080' }],
});

console.log(socialPost.id);

Request & Response types

This library includes TypeScript definitions for all request params and response fields. You may import and use them like so:```ts
import PostForMe from 'post-for-me';

const client = new PostForMe({
apiKey: process.env['POST_FOR_ME_API_KEY'], // This is the default and can be omitted
});

const params: PostForMe.SocialPostCreateParams = {
caption: 'My first post!',
social_accounts: ['sa_1234'],
media: [{ url: 'https://picsum.photos/1080' }],
};
const socialPost: PostForMe.SocialPost = await client.socialPosts.create(params);


Documentation for each method, request param, and response field are available in docstrings and will appear on hover in most modern editors.

## Handling errors

When the library is unable to connect to the API,
or if the API returns a non-success status code (i.e., 4xx or 5xx response),
a subclass of `APIError` will be thrown:```ts
const socialPost = await client.socialPosts
  .create({
    caption: 'My first post!',
    social_accounts: ['sa_1234'],
    media: [{ url: 'https://picsum.photos/1080' }],
  })
  .catch(async (err) => {
    if (err instanceof PostForMe.APIError) {
      console.log(err.status); // 400
      console.log(err.name); // BadRequestError
      console.log(err.headers); // {server: 'nginx', ...}
    } else {
      throw err;
    }
  });

Error codes are as follows:

Status Code Error Type
400 BadRequestError
401 AuthenticationError
403 PermissionDeniedError
404 NotFoundError
422 UnprocessableEntityError
429 RateLimitError
>=500 InternalServerError
N/A APIConnectionError

Retries

Certain errors will be automatically retried 2 times by default, with a short exponential backoff.
Connection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict,
429 Rate Limit, and >=500 Internal errors will all be retried by default.

You can use the maxRetries option to configure or disable this:```js
// Configure the default for all requests:
const client = new PostForMe({
maxRetries: 0, // default is 2
});

// Or, configure per-request:
await client.socialPosts.create({
caption: 'My first post!',
social_accounts: ['sa_1234'],
media: [{ url: 'https://picsum.photos/1080' }],
}, {
maxRetries: 5,
});


### Timeouts

Requests time out after 1 minute by default. You can configure this with a `timeout` option:```ts
// Configure the default for all requests:
const client = new PostForMe({
  timeout: 20 * 1000, // 20 seconds (default is 1 minute)
});

// Override per-request:
await client.socialPosts.create({
  caption: 'My first post!',
  social_accounts: ['sa_1234'],
  media: [{ url: 'https://picsum.photos/1080' }],
}, {
  timeout: 5 * 1000,
});

On timeout, an APIConnectionTimeoutError is thrown.

Note that requests which time out will be retried twice by default.

Advanced Usage

Accessing raw Response data (e.g., headers)

The "raw" Response returned by fetch() can be accessed through the .asResponse() method on the APIPromise type that all methods return.
This method returns as soon as the headers for a successful response are received and does not consume the response body, so you are free to write custom parsing or streaming logic.

You can also use the .withResponse() method to get the raw Response along with the parsed data.
Unlike .asResponse() this method consumes the body, returning once it is parsed.```ts
const client = new PostForMe();

const response = await client.socialPosts
.create({
caption: 'My first post!',
social_accounts: ['sa_1234'],
media: [{ url: 'https://picsum.photos/1080' }],
})
.asResponse();
console.log(response.headers.get('X-My-Header'));
console.log(response.statusText); // access the underlying Response object

const { data: socialPost, response: raw } = await client.socialPosts
.create({
caption: 'My first post!',
social_accounts: ['sa_1234'],
media: [{ url: 'https://picsum.photos/1080' }],
})
.withResponse();
console.log(raw.headers.get('X-My-Header'));
console.log(socialPost.id);


### Logging

> [!IMPORTANT]
> All log messages are intended for debugging only. The format and content of log messages
> may change between releases.

#### Log levels

The log level can be configured in two ways:

1. Via the `POST_FOR_ME_LOG` environment variable
2. Using the `logLevel` client option (overrides the environment variable if set)```ts
import PostForMe from 'post-for-me';

const client = new PostForMe({
  logLevel: 'debug', // Show all log messages
});

Available log levels, from most to least verbose:

  • 'debug' - Show debug messages, info, warnings, and errors
  • 'info' - Show info messages, warnings, and errors
  • 'warn' - Show warnings and errors (default)
  • 'error' - Show only errors
  • 'off' - Disable all logging

At the 'debug' level, all HTTP requests and responses are logged, including headers and bodies.
Some authentication-related headers are redacted, but sensitive data in request and response bodies
may still be visible.

Custom logger

By default, this library logs to globalThis.console. You can also provide a custom logger.
Most logging libraries are supported, including pino, winston, bunyan, consola, signale, and @std/log. If your logger doesn't work, please open an issue.

When providing a custom logger, the logLevel option still controls which messages are emitted, messages
below the configured level will not be sent to your logger.```ts
import PostForMe from 'post-for-me';
import pino from 'pino';

const logger = pino();

const client = new PostForMe({
logger: logger.child({ name: 'PostForMe' }),
logLevel: 'debug', // Send all messages to pino, allowing it to filter
});


### Making custom/undocumented requests

This library is typed for convenient access to the documented API. If you need to access undocumented
endpoints, params, or response properties, the library can still be used.

#### Undocumented endpoints

To make requests to undocumented endpoints, you can use `client.get`, `client.post`, and other HTTP verbs.
Options on the client, such as retries, will be respected when making these requests.```ts
await client.post('/some/path', {
  body: { some_prop: 'foo' },
  query: { some_query_arg: 'bar' },
});

Undocumented request params

To make requests using undocumented parameters, you may use // @ts-expect-error on the undocumented
parameter. This library doesn't validate at runtime that the request matches the type, so any extra values you
send will be sent as-is.```ts
client.socialPosts.create({
// ...
// @ts-expect-error baz is not yet public
baz: 'undocumented option',
});


For requests with the `GET` verb, any extra params will be in the query, all other requests will send the
extra param in the body.

If you want to explicitly send an extra argument, you can do so with the `query`, `body`, and `headers` request
options.

#### Undocumented response properties

To access undocumented response properties, you may access the response object with `// @ts-expect-error` on
the response object, or cast the response object to the requisite type. Like the request params, we do not
validate or strip extra properties from the response from the API.

### Customizing the fetch client

By default, this library expects a global `fetch` function is defined.

If you want to use a different `fetch` function, you can either polyfill the global:```ts
import fetch from 'my-fetch';

globalThis.fetch = fetch;

Or pass it to the client:```ts
import PostForMe from 'post-for-me';
import fetch from 'my-fetch';

const client = new PostForMe({ fetch });


### Fetch options

If you want to set custom `fetch` options without overriding the `fetch` function, you can provide a `fetchOptions` object when instantiating the client or making a request. (Request-specific options override client options.)```ts
import PostForMe from 'post-for-me';

const client = new PostForMe({
  fetchOptions: {
    // `RequestInit` options
  },
});

Configuring proxies

To modify proxy behavior, you can provide custom fetchOptions that add runtime-specific proxy
options to requests:

Node [docs]```ts
import PostForMe from 'post-for-me';
import * as undici from 'undici';

const proxyAgent = new undici.ProxyAgent('http://localhost:8888');
const client = new PostForMe({
fetchOptions: {
dispatcher: proxyAgent,
},
});


 **Bun** [docs]```ts
import PostForMe from 'post-for-me';

const client = new PostForMe({
  fetchOptions: {
    proxy: 'http://localhost:8888',
  },
});

Deno [docs]```ts
import PostForMe from 'npm:post-for-me';

const httpClient = Deno.createHttpClient({ proxy: { url: 'http://localhost:8888' } });
const client = new PostForMe({
fetchOptions: {
client: httpClient,
},
});
```

Frequently Asked Questions

Semantic versioning

This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:

  1. Changes that only affect static types, without breaking runtime behavior.
  2. Changes to library internals which are technically public but not intended or documented for external use. (Please open a GitHub issue to let us know if you are relying on such internals.)
  3. Changes that we do not expect to impact the vast majority of users in practice.

We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.

We are keen for your feedback; please open an issue with questions, bugs, or suggestions.

Requirements

TypeScript >= 4.9 is supported.

The following runtimes are supported:

  • Web browsers (Up-to-date Chrome, Firefox, Safari, Edge, and more)
  • Node.js 20 LTS or later (non-EOL) versions.
  • Deno v1.28.0 or higher.
  • Bun 1.0 or later.
  • Cloudflare Workers.
  • Vercel Edge Runtime.
  • Jest 28 or greater with the "node" environment ("jsdom" is not supported at this time).
  • Nitro v2.6 or greater.

Note that React Native is not supported at this time.

If you are interested in other runtime environments, please open or upvote an issue on GitHub.

Contributing

See the contributing documentation.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Post For Me 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Post For Me 怎么在 Cursor、VS Code、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Post For Me 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Post For Me 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Post For Me 支持哪些客户端?

资料标注支持 Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Post For Me 能提供哪些能力?

资料显示能力标签包括 social media、posting、analytics、feeds、tiktok、x。具体工具清单以官方文档为准。

Post For Me 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。