Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者による説明(英語の原文)
Official ParseAPI MCP. Place, IP, email, phone, weather lookups.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
PARSEAPI_KEY, PARSEAPI_MCP_MODE, X-API-Key「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
このアドレスはリクエストの header にキーが必要ですが、コネクタを追加するメニューでは設定できません。代わりにClaude Code、Cursor、VS Codeを使ってください。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"parseapi": {
"command": "npx",
"args": [
"-y",
"parseapi-mcp"
],
"env": {
"PARSEAPI_KEY": "your-value",
"PARSEAPI_MCP_MODE": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add --transport http parseapi https://mcp.parseapi.com --header 'X-API-Key: your-value'claude mcp add parseapi --env PARSEAPI_KEY=your-value --env PARSEAPI_MCP_MODE=your-value -- npx -y parseapi-mcp動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"parseapi": {
"url": "https://mcp.parseapi.com",
"headers": {
"X-API-Key": "your-value"
}
}
}
}プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"parseapi": {
"command": "npx",
"args": [
"-y",
"parseapi-mcp"
],
"env": {
"PARSEAPI_KEY": "your-value",
"PARSEAPI_MCP_MODE": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"parseapi": {
"type": "http",
"url": "https://mcp.parseapi.com",
"headers": {
"X-API-Key": "your-value"
}
}
}
}プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"parseapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"parseapi-mcp"
],
"env": {
"PARSEAPI_KEY": "your-value",
"PARSEAPI_MCP_MODE": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
このアドレスはリクエストの header にキーが必要ですが、コネクタを追加するメニューでは設定できません。代わりにClaude Code、Cursor、VS Codeを使ってください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
PARSEAPI_MCP_MODE envX-API-Key 秘密 HTTP headerこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーは、ツール一覧を表示する前にサインインを求めます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名はドメイン parseapi.com で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
164ミリ秒で応答(HTTP 401)
OAuthでのサインインに対応しているため、AIアプリがログイン画面へ案内してくれます
まだチェックしていません。エンドポイントをチェックするときにツール一覧を読み取ります
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:PARSEAPI_KEY, X-API-Key
どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。
GitHubリポジトリの最終更新は–、最新バージョン(1.12.4)がレジストリに届いたのは5 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:Vexa, emailmd, MCP WhatsApp Cloud
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Official ParseAPI MCP server. Look up places, addresses, companies, email, phone, weather, timezones, dates and more from your AI agent.
One URL, nothing to install. Add the server and sign in once in the browser. Free plan works.
{
"mcpServers": { "parseAPI": { "url": "https://mcp.parseapi.com" } } }
Cursor: Add to Cursor
Repo-root .mcp.json is keyless on purpose. cursor.directory auto-detects it when you submit or refresh the listing.
CI and headless setups skip the browser with a key from parseapi.com:
{
"mcpServers": { "parseAPI": { "url": "https://mcp.parseapi.com", "headers": { "X-API-Key": "your-api-key" } } } }
{
"mcpServers": { "parseAPI": { "command": "npx", "args": ["-y", "parseapi-mcp"], "env": { "PARSEAPI_KEY": "your-api-key" } } } }
Since version 1.0.0, the package explicitly selects the API contract supported by this MCP package. Every API tool request sends Parse-Version: 2.0.0, matching this release's tool descriptions and SDK response types. The contract is fixed for both local stdio and hosted HTTP, including retries. Your key, OAuth identity and team's saved default stay the same.
For local stdio, pin the MCP package version in your application configuration and test the new release before deploying it. A future major MCP upgrade can select a newer API contract. There is no version argument to add to individual tool calls. The hosted service uses the API contract supported by its deployed MCP release.
MCP packages older than 1.0.0 keep their existing behavior and use the team's default. Keep that default unchanged while older applications depend on it. Rolling back to a package without a version header restores the team default, so rollback only restores the old contract when that default has stayed unchanged. See API versions and migration.
Country uses iso_alpha3 and iso_numeric, State uses the full iso_subdivision code such as US-CA, Language uses iso_alpha3, and Currency uses iso_numeric. Primary country, state, language and currency codes keep their meaning. Results retain the selected API contract's exact keys, values, nulls and nesting. Earlier server contracts retain their earlier ISO spellings. Use the existing lookup methods for each resource.
Full mode provides 68 local lookup tools and 67 hosted lookup tools, plus discover for local metadata and preflight for authenticated task estimates. ip_self is local only. time returns current local time and Unix seconds. It accepts a timezone or coordinates and defaults to UTC when both are omitted. date parses the supplied date, or returns today in UTC when omitted. Existing timezone calls remain supported with their original arguments. Every lookup returns the JSON the API serves.
Tools follow the lookup names: country_states, city_search, postal_nearby, address, address_search, company, company_id, company_search, company_coverage, email, card, industry, industry_search, dns, asn, currency_rate, and the rest. Text searches take query. Company directory search supports one name/domain/ticker/identifier selector or country/exact-SIC discovery filters.
The existing naics and naics_search tools remain available as compatibility names for Industry.
Industry paid deep records include classification deep.exclusions, each with a description and linked codes. Generic exclusions can have no linked codes. Omitted or null exclusions in older responses remain unknown. Search results also include match: the matched field (name, term or naics) and text, plus corrections with from and to tokens for typo fallback. Corrections are empty for exact, plural and prefix matches. Direct code lookups omit match. Older responses may omit it.
Example tool arguments:
| Tool | Arguments | |
|---|---|---|
stack | {"domain":"example.com"} (website technologies and versions by category) | |
domain | {"domain":"example.com"} (registration status) | |
domain | {"domain":"example.com","deep":true} (registration details on paid plans) | |
dns | {"domain":"example.com","type":"TXT"} | |
mx | {"domain":"example.com"} | |
asn | {"asn":"AS13335"} | |
card | {"bin":"424242"} | |
country_states | {"code":"US"} | |
address_search | {"query":"1600 Pennsylvania","country":"US","city":"Washington","state":"DC"} | |
company_search | {"query":"Cloudflare","country":"US"} | |
company_id | {"id":"co_xw3f22es6cjq","deep":true} | |
company_coverage | {} | |
time | {} (UTC now) | |
time | {"timezone":"America/New_York","at":"2026-09-05T09:00:00","to":"Asia/Tokyo"} | |
time | {"lat":40.71,"lon":-74.01} | |
time | {"timezone":"UTC","targets":["America/New_York","Asia/Tokyo"]} | |
time_zones | {"query":"New York"} | |
time | {"timezone":"America/New_York","at":"2026-11-01T01:30:00","to":"UTC","disambiguation":"later"} | |
date | {"date":"03/04/2026","format":"dmy"} | |
elevation | {"lat":35.2271,"lon":-80.8431} | |
elevation | `{"points":"39.7392,-104.9903 | 39.75,-104.98"}` |
elevation | `{"path":"39.7392,-104.9903 | 39.75,-104.98","samples":100}` |
Time uses disambiguation only for offsetless at with to or targets. The default compatible selects the earlier repeated time or advances a skipped time. earlier and later choose the respective instant. reject returns ambiguous_time for repeated times and nonexistent_time for skipped times. Prefer it for user-entered appointments. Ask for an explicit offset or the user's choice before retrying a rejected local time. Explicit offsets select an instant directly. Time Deep is available on paid plans in the same pooled request. Existing accounts retain their current Deep access.
Time Deep includes nullable resolution. Resolution reports kind (unique, overlap or gap), policy, signed adjustment_seconds, and chronological alternatives with exact local at, Unix seconds and UTC offset. Unique wall times have no alternatives. Explicit-offset timestamps, current clocks, non-conversion lookups and unknown source zones have null resolution.
Elevation accepts exactly one of lat and lon, points, or path with samples. A point list supports up to 512 points per local batch as lat,lon pairs separated by |, or enc: followed by a Google encoded polyline, with at most 12000 characters. The points response array preserves input order and duplicate coordinates. Each sample includes meters, feet and grid resolution in meters. Unknown samples stay null. An accepted local list uses one pooled request, with JSON POST selected automatically for long URLs.
A path uses the same string formats with 2-512 vertices and a required integer samples count from 2 to 512. The response points include both endpoints, spaced uniformly by cumulative great-circle distance along the path. Each segment follows the shortest arc. A segment with antipodal endpoints is rejected because it does not define a unique arc. An accepted local path uses one pooled request. samples is invalid with a single coordinate or a point list.
Each local batch is limited to 25 km between any two coordinates and 12 distinct terrain files in total across the fine grid and all possible global fallback files. For paths, both the supplied vertices and generated samples must fit the 25 km span. The terrain file budget applies to the sampled coordinates. This is a span limit, not a limit on cumulative path length. Send longer or more spread-out routes in shorter sections. An over-limit batch returns HTTP 400. MCP does not silently split or discard coordinates.
Australian postal lookup returns core localities with suburb choices (city, state, state_name). Null or an omitted field means unknown, while [] means the reviewed reference has no eligible choices. A single choice can coexist with city: null. Ask for the user's suburb choice and preserve manual entry. These are geographic choices, not mailing-address verification. AU Postal tool results include a separate source notice after the JSON. G-NAF source, adaptations and licence.
Address lookup returns standardized components and registration status for the US and France. Its deep object is currently empty. address_search also accepts postal and ip to narrow or rank matches. French search needs country: "FR" and either postal or city.
For the company directory, call company_search with at most one of query, domain, ticker or identifier. Use exchange with a ticker and authority with an identifier. Review the candidates, then pass the chosen id to company_id. Send the returned next as cursor with the same selector, filters and limit for another page. Directory Deep adds detail to each company result on paid plans in the same pooled request. Existing accounts retain their current Deep access. Selected website descriptions, logos, socials and founding claims are returned where available. Logo URLs are returned without fetching images. Directory tools do not accept lang. company_coverage describes the edition's records, and empty listings do not establish private ownership. The company tool remains listed for compatibility, but national-number lookups are retired on the public API. Use company_search and company_id for maintained public-company records.
For discovery without an identity selector, supply country or both industry and industry_type. For example: { "country": "US", "industry": "0700", "industry_type": "sic" }. SIC is the supported namespace; its exact four-digit code stays a string. Empty requests, incomplete industry pairs and multiple selectors are rejected. Country means the profile country. Filters intersect, unknown values do not match, and the same filters and limit must accompany a returned cursor. Filter-only candidates carry match: { "field": "filters", "value": null }.
Ordinary lookups retry up to twice after a transient failure. A valid Retry-After is honored when the wait is at most five seconds; longer waits return the API error immediately without retrying early. When the response supplies this header, the error includes retry_after with its original seconds or HTTP-date value. Metered lookups and address deep checks default to no retries. Cancelling a tool call cancels the pending SDK request.
Errors come back as JSON with a machine-readable code. Branch on code, never on message text. A miss is not_found. No key is invalid_api_key.
Ask discover what an operation can determine before making a lookup:
{ "operation": "email" }
The result includes the actual input schema and reviewed policies for capabilities, freshness, uncertainty, billing units, credential types and retries. Both JSON text and MCP structuredContent carry the same result. Email, Domain, DNS, MX, Country, Time and timezone discovery have reviewed policies. Other operations return their input schema with policy: null. Field meanings are specific to each operation. An unknown result is not automatically a reason to retry.
Use { "query": "mailbox" } to find operations. Search returns up to five summaries by default. detail: "full" includes schemas and policies. Use limit and the returned next_offset to page through results. Metadata calls make no API requests and consume no lookup units. Hosted HTTP still requires its existing authentication before discovery.
Policies describe the API contract. `
冒頭だけを表示しています。続きはリポジトリで読めます