Live

Nextdoor logo

Nextdoor API and MCP server

nextdoor.com

Nextdoor has no open API for running a Business Page (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Nextdoor with 13 endpoints (8 read, 5 write): your AI agent signs in as you and does the work.

Endpoints
13 8 read, 5 write
Updated
How Cotlet connects your agent to Nextdoor
  1. Your agent

    Claude Code, Codex, Cursor or a script

  2. Cotlet

    MCP server and REST API · 13 endpoints

    cotlet.dev/mcp/v1

  3. Nextdoor logo

    Nextdoor

    Signed in as you on nextdoor.com

You sign in once. We never store your password.

Official API

Does Nextdoor have an official API?

Nextdoor has no open API for running a Business Page (checked 11 Oct 2026). Its Publish API is write-only and partners must apply for access, the open Share plugin only shares content into Nextdoor, and the Nextdoor app on Zapier has one trigger (New Lead) and no actions.

What Nextdoor's own tools do compared with Cotlet
Task Nextdoor official Cotlet
Publish a business post Partly Approved Publish API partners only; the open Share plugin only shares content into Nextdoor Yes
Read your posts and their comments No Yes
Reply to comments on your posts No Yes
List recommendations No Yes
Reply to recommendations No Yes
Read and answer Business Page messages No Yes
Delete a business post No Yes
Get your Business Page details No Yes

Sources: Nextdoor developer docs: sharing overview · Nextdoor for Business: Business Posts · Nextdoor on Zapier · Nextdoor Help: Create a business post on Nextdoor

Common use cases

What can an AI agent do in Nextdoor?

Cotlet is best for local businesses and agencies that post, answer recommendations and reply to neighbors on Nextdoor without running or fixing a server.

  • Reply to Nextdoor recommendations Runs: Weekly

    Thank everyone who recommended us since last Monday, by name and job, and hold any negative recommendation for me as a draft. Your agent calls list_recommendations and reply_to_recommendation.

  • Publish Nextdoor business posts Runs: Weekly

    Write this week's Nextdoor post from my notes on the fall gutter checks, make sure it does not repeat a recent post, and publish it after I approve. Your agent calls get_business_page, list_posts and create_post.

  • Answer comments and messages from neighbors Runs: Daily

    Answer the open questions under our Nextdoor posts and in the page chats. Ask me before you quote a price or a date. Your agent calls list_posts, list_comments, reply_to_comment, list_conversations, get_conversation and send_message.

  • Answer Business Page messages Runs: Daily

    Which messages to our page are still waiting for a reply? Draft answers for me. Your agent calls list_conversations, get_conversation and send_message.

  • Get your recommendation link

    Give me our Business Page link so I can add it to the invoice email. Your agent calls get_page_share_link.

Endpoints

What is the Nextdoor API?

Cotlet's Nextdoor API exposes 13 endpoints for your own Nextdoor account: get Business Page, list posts, get post, list comments, list recommendations, get page share link, list conversations, get conversation, create post, reply to comment, reply to recommendation, send message and delete post. The get_business_page endpoint returns your page: name, category, contact details, neighborhoods, recommendation and Fave counts. Each endpoint takes simple JSON inputs like body, limit or post_id and works both as an MCP tool for agents and as a REST call for scripts.

All endpoints · 13 total

missing one? request an endpoint

  • POST

    get_business_page

    read

    Returns the page the signed-in account manages. Use the neighborhoods it lists as the audience for create_post. The call fails if the account has no claimed Business Page.

    POST /api/v1/nextdoor/get_business_page

    Input

    No parameters.

    Example response

    {
      "page_id": "pg_2204",
      "name": "Clearwater Gutter Care",
      "category": "Gutter cleaning",
      "phone": "+1 555 0142",
      "neighborhoods": [
        "Maple Hill",
        "Oak Park",
        "Riverside"
      ],
      "recommendations": 41,
      "faves": 118
    }
  • POST

    list_posts

    read

    Returns each post with title, text, audience, reactions and comment count. Nextdoor's Post Insights are not available for business posts, so there are no view counts. Use the cursor to read older posts.

    POST /api/v1/nextdoor/list_posts

    Input

    Input: list_posts
    Parameter Type Description
    limit integer Number of posts per call. Default: 20.
    cursor string Next page cursor from the previous call.

    Example response

    {
      "posts": [
        {
          "post_id": "bp_8812046",
          "title": "Open house this Saturday",
          "reactions": 12,
          "comments": 3,
          "created_at": "2026-10-08T09:30:00Z"
        },
        {
          "post_id": "bp_8790311",
          "title": "Fall gutter checks",
          "reactions": 7,
          "comments": 1,
          "created_at": "2026-10-01T08:00:00Z"
        }
      ],
      "next_cursor": null
    }
  • POST

    get_post

    read

    Returns the full text and the audience (distance or neighborhoods) the post was published to. Comments are read with list_comments.

    POST /api/v1/nextdoor/get_post

    Input

    Input: get_post
    Parameter Type Description
    post_id required string Post ID from list_posts.

    Example response

    {
      "post_id": "bp_8812046",
      "title": "Open house this Saturday",
      "body": "Drop by 10:00 to 14:00 for free coffee and a look at the new workshop.",
      "neighborhoods": [
        "Maple Hill",
        "Oak Park"
      ],
      "reactions": 12,
      "comments": 3
    }
  • POST

    list_comments

    read

    Returns comments oldest first, so your agent reads the discussion in order. Each comment has the ID that reply_to_comment needs.

    POST /api/v1/nextdoor/list_comments

    Input

    Input: list_comments
    Parameter Type Description
    post_id required string Post ID from list_posts.
    unanswered_only boolean Skip comments you already replied to.

    Example response

    {
      "comments": [
        {
          "comment_id": "cm_77120",
          "author": "Priya S.",
          "neighborhood": "Maple Hill",
          "body": "Do you service Maple Hill?",
          "replied": false
        }
      ]
    }
  • POST

    list_recommendations

    read

    Returns newest first. Each recommendation has the ID that reply_to_recommendation needs, and your existing reply if you wrote one.

    POST /api/v1/nextdoor/list_recommendations

    Input

    Input: list_recommendations
    Parameter Type Description
    since date Only recommendations on or after this date.
    unanswered_only boolean Skip recommendations you already replied to.
    limit integer Number of recommendations per call. Default: 50.

    Example response

    {
      "recommendations": [
        {
          "recommendation_id": "rec_30418",
          "author": "Dana K.",
          "neighborhood": "Oak Park",
          "body": "Cleaned our gutters in one morning and left the yard spotless.",
          "date": "2026-10-06",
          "reply": null
        }
      ]
    }
  • POST

    list_conversations

    read

    Returns the most recent threads first. Neighbors start these conversations; a business cannot start one.

    POST /api/v1/nextdoor/list_conversations

    Input

    Input: list_conversations
    Parameter Type Description
    unanswered_only boolean Only threads where the last message is not yours.
    limit integer Number of threads per call. Default: 20.

    Example response

    {
      "conversations": [
        {
          "conversation_id": "conv_5530",
          "neighbor": "Priya S.",
          "last_message": "Can you come Thursday morning?",
          "last_from": "neighbor",
          "updated_at": "2026-10-10T16:12:00Z"
        }
      ]
    }
  • POST

    get_conversation

    read

    Returns the messages oldest first. Reading a thread does not send anything.

    POST /api/v1/nextdoor/get_conversation

    Input

    Input: get_conversation
    Parameter Type Description
    conversation_id required string Conversation ID from list_conversations.

    Example response

    {
      "conversation_id": "conv_5530",
      "neighbor": "Priya S.",
      "messages": [
        {
          "from": "neighbor",
          "body": "Hi, do you do gutter guards?",
          "sent_at": "2026-10-10T15:58:00Z"
        },
        {
          "from": "business",
          "body": "Yes, we do. What is the address?",
          "sent_at": "2026-10-10T16:05:00Z"
        },
        {
          "from": "neighbor",
          "body": "Can you come Thursday morning?",
          "sent_at": "2026-10-10T16:12:00Z"
        }
      ]
    }
  • POST

    create_post

    write

    Publishes a post with a title and a description. Nextdoor's help center says business posts have no fixed radius and reach neighbors through engagement and Faves; radius and neighborhoods apply only where the post form still offers audience settings. The call fails for accounts Nextdoor still asks to verify business documents. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/nextdoor/create_post

    Input

    Input: create_post
    Parameter Type Description
    title required string Post title.
    body required string Post description.
    radius integer Reach neighborhoods within this distance of your business, as in the post audience settings.
    neighborhoods string[] Neighborhood names to add or remove, from get_business_page.

    Example response

    {
      "post_id": "bp_8812046",
      "status": "published",
      "neighborhoods": 14,
      "url": "https://nextdoor.com/p/yourname-open-house"
    }
  • POST

    reply_to_comment

    write

    The reply is public and appears under your business name. Only the author or the page administrator can edit or delete it later. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/nextdoor/reply_to_comment

    Input

    Input: reply_to_comment
    Parameter Type Description
    comment_id required string Comment ID from list_comments.
    body required string Reply text.

    Example response

    {
      "reply_id": "cm_77135",
      "comment_id": "cm_77120",
      "status": "published"
    }
  • POST

    reply_to_recommendation

    write

    The reply is public and appears under the recommendation as your business, not your personal profile. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/nextdoor/reply_to_recommendation

    Input

    Input: reply_to_recommendation
    Parameter Type Description
    recommendation_id required string Recommendation ID from list_recommendations.
    body required string Reply text.

    Example response

    {
      "reply_id": "rr_9120",
      "recommendation_id": "rec_30418",
      "status": "published"
    }
  • POST

    send_message

    write

    Works only in a conversation the neighbor started. A business cannot message a neighbor first, and Nextdoor bans unsolicited promotional messages. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/nextdoor/send_message

    Input

    Input: send_message
    Parameter Type Description
    conversation_id required string Conversation ID from list_conversations.
    body required string Message text.

    Example response

    {
      "message_id": "msg_88410",
      "conversation_id": "conv_5530",
      "status": "sent"
    }
  • POST

    delete_post

    write

    Removes the post from the newsfeed. Only the author or the page administrator can delete a post. A deleted post cannot be restored with one call. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/nextdoor/delete_post

    Input

    Input: delete_post
    Parameter Type Description
    post_id required string Post ID from list_posts.

    Example response

    {
      "post_id": "bp_8790311",
      "status": "deleted"
    }

Setup

How do I connect Nextdoor to Claude Code, Codex or Cursor?

Connecting Nextdoor takes three steps: request access, sign in to Nextdoor once, then add one MCP server or call the REST API with the same key.

Connect Nextdoor over MCP

  1. 1

    Create an account

    Sign up and add Nextdoor in the console. Your API key is there too.

  2. 2

    Sign in to Nextdoor once

    Open the connect page from the console and sign in to Nextdoor the way you always do. We keep the session, never your password, and you can revoke it anytime.

  3. 3

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

  4. 4

    Ask your agent

    Prompt

    Thank everyone who recommended us since last Monday, by name and job, and hold any negative recommendation for me as a draft.

    Ask in plain words. Your agent finds the Nextdoor tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

Call Nextdoor over REST

  1. 1

    Export your API key

    Shell

    export COTLET_API_KEY="cotlet_..."

    Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

  2. 2

    Call a tool

    curl

    curl https://cotlet.dev/api/v1/nextdoor/create_post \
      -H "Authorization: Bearer $COTLET_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"title":"Open house this Saturday","body":"Drop by 10:00 to 14:00 for free coffee and a look at the new workshop.","radius":3}'

    Every tool is a POST endpoint at /api/v1/nextdoor/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

  3. 3

    Read the result

    Example response · create_post

    {
      "post_id": "bp_8812046",
      "status": "published",
      "neighborhoods": 14,
      "url": "https://nextdoor.com/p/yourname-open-house"
    }

    You get plain JSON back, ready for your script. A failed call costs nothing.

Why Cotlet

Why use Cotlet for Nextdoor? Hosted, safe and kept working.

  • Built for agents

    • One MCP server for every app you connect.
    • The same tools as a REST API for scripts and cron jobs.
    • Works with Claude Code, Codex and Cursor.
  • Your login stays yours

    • You sign in to Nextdoor yourself. We keep only the session, encrypted with AES-256.
    • The model never sees a login.
    • No stored passwords, no CAPTCHA solving, no MFA bypass.
  • You stay in control

    • Pick read only, or read and write.
    • Anything that reaches other people waits for your OK, unless you switch it off per tool.
    • Revoke access in one click.
  • Kept working for you

    • We test every integration daily.
    • When Nextdoor changes, the tool pauses until we fix it.
    • Failed calls cost nothing.

Alternatives

Is there a Nextdoor MCP server on GitHub?

Yes. Open-source Nextdoor MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it your Nextdoor login, and fix it when Nextdoor changes its site. Cotlet hosts the same kind of server for you, and our team keeps it working.

Cotlet compared with a GitHub MCP server
GitHub MCP server Cotlet
Setup Clone the repo, install it, sign it in to Nextdoor, add it to each MCP client Request access, sign in to Nextdoor once, add one MCP server or API key
When Nextdoor changes It breaks until you or the maintainer fix it Our team tests it daily and fixes it for you; failed calls are free
Your Nextdoor session Your login details or session in a file or config on your side Session only, never your password, encrypted in an EU vault and revoked in one click
When the session expires Tools fail until you sign in again by hand If Nextdoor logs you out, your agent gets a link to sign in again
Upkeep You update, monitor and debug it yourself Nothing to host or update
Where it runs Your computer, while it is on Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule
Price Free, paid for with your time Free 7-day trial with 5,000 credits, then credits per call

Which one fits you

Pick Cotlet if

  • you are not a developer, or you do not want to maintain a server
  • you need it to keep working when Nextdoor changes, without checking it yourself
  • your agent or a script should run it on a schedule, also while your computer is off

Pick an open-source server if

  • you are comfortable installing, updating and fixing it yourself
  • you want the session to stay on your own computer
  • you only need it now and then, from one MCP client

For AI agents

Cotlet for Nextdoor in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Endpoint health

verified 2h ago

  • get_business_page passing
  • list_posts passing
  • get_post passing
  • list_comments passing
  • list_recommendations passing

+ 8 more endpoints

13/13 passing latest check self-healing

nextdoor.txt

Nextdoor has no open API for running a Business Page (checked 11 Oct 2026). Its Publish API is write-only and partners must apply for access, the open Share plugin only shares content into Nextdoor, and the Nextdoor app on Zapier has one trigger (New Lead) and no actions.
Cotlet provides a hosted MCP server and REST API for Nextdoor: 13 tools (8 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=nextdoor; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/nextdoor
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        get_business_page, list_posts, get_post, list_comments, list_recommendations, get_page_share_link, list_conversations, get_conversation, create_post, reply_to_comment, reply_to_recommendation, send_message, delete_post
Confirm      create_post, reply_to_comment, reply_to_recommendation, send_message, delete_post (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/nextdoor-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=nextdoor (Nextdoor is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Nextdoor once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Nextdoor server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Nextdoor MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Nextdoor in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Nextdoor's terms; Cotlet is not affiliated with Nextdoor.
Full page as Markdown

Automations

Can Nextdoor automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Nextdoor connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to reply to nextdoor recommendations, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

Where to run Nextdoor automations through Cotlet, and how to schedule them
Where How to connect How to schedule
Your AI agent Add https://cotlet.dev/mcp/v1 with your API key. A scheduled agent run, for example a Claude Code routine.
n8n MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/nextdoor/{tool}. Schedule Trigger node.
Make HTTP module: POST https://cotlet.dev/api/v1/nextdoor/{tool} with an Authorization: Bearer header and a JSON body. Scenario schedule.
Zapier Webhooks by Zapier: POST https://cotlet.dev/api/v1/nextdoor/{tool} with the same header and body. Schedule by Zapier trigger.
Your own script POST https://cotlet.dev/api/v1/nextdoor/{tool} with your API key. cron or GitHub Actions.

Pricing & limits

How much does the Nextdoor API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Nextdoor API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

Cotlet plan sizes: price, monthly credits and price per credit
Size Price Credits / month Per credit
Solo $29/mo 3,000 about $0.0097
Pro $99/mo 12,000 about $0.0083
Agency $299/mo 40,000 $0.0075

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.

About Cotlet

How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Nextdoor account.

Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to Nextdoor yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Nextdoor tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect Nextdoor in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do
Store passwords, solve CAPTCHAs or bypass MFA.
Nextdoor's terms
You use your own Nextdoor account and stay responsible for following Nextdoor's terms. Cotlet is independent and not affiliated with Nextdoor. Terms
Contact
Questions about the company, security or an app: contact@cotlet.dev
About Cotlet

Frequently asked questions

How do I get access?

Request access and pick Nextdoor. Cotlet reviews each request and emails you your API key.

Do I need to be technical?

No. You sign in to Nextdoor once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

Is a hosted server safe? My Nextdoor session would leave my computer.

Cotlet keeps your Nextdoor session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

Can it message neighbors first?

No. Nextdoor's help center says a business cannot message neighbors, and its self-promotion policy bans unsolicited promotional messages. send_message replies only in conversations a neighbor started.

Do I need a verified business to post?

Nextdoor asks casual service providers, such as dog walkers or babysitters, to verify with official business documents before they post to the neighborhood newsfeed. Verify in Nextdoor first; then create_post works.

Can my agent post or send messages in Nextdoor without asking me?

No. Every call to create_post, reply_to_comment, reply_to_recommendation, send_message or delete_post waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

Can I use the Nextdoor API in n8n?

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/nextdoor/{tool} from the HTTP Request node.

Give your agent access to Nextdoor.

Request access and pick it. We review each request and email you your API key. Free 7-day trial with 5,000 credits, no card needed.