docs: add Meteora AI tooling

[flashxbtbot]

Summary

• Add Meteora's official Documentation MCP / AI skill to the DeFi AI coding skills list.
• Add Meteora Documentation MCP to Developer Tools for agentic docs search and read-only docs filesystem access.
• Reference the core Meteora AMM surfaces agents need for high-signal integrations: DLMM, DAMM v2, Dynamic Bonding Curve, and their TypeScript SDKs.

Notes

• The DLMM core program was reviewed with maintainer-provided access, but the public listing links to the DLMM developer guide so awesome-solana-ai readers land on an accessible public resource.
• DAMM v2 and DBC entries link directly to their public program repositories and SDKs.

Validation

• Verified all added public links return HTTP 200.
• Ran git diff --check.

[greptile-apps]

Greptile Summary

This PR adds two new Meteora entries to README.md: one in the DeFi AI Coding Skills section (meteora-ai-skill-and-mcp) and one in the Developer Tools section (Meteora Documentation MCP), both covering Meteora's DLMM, DAMM v2, and Dynamic Bonding Curve surfaces.

• Both new entries point to https://docs.meteora.ag/mcp, which means the DeFi skills entry resolves to the same page as the Developer Tools entry; DeFi skill entries elsewhere in the file link to a skill source repo rather than a documentation site.
• The DeFi entry's description contains six embedded Markdown hyperlinks, which is inconsistent with the plain-text description style used by every other entry in the file.

Confidence Score: 4/5

Documentation-only change; no code is modified. The main concern is that both new entries point to the same URL, making the DeFi skills listing redundant with the Developer Tools listing.

The DeFi skill entry links to the MCP documentation page rather than a skill source repository, which is how every other skill entry in that section works and what distinguishes skills from developer tools. This creates a confusing duplicate rather than a distinct resource for readers.

README.md — specifically the new meteora-ai-skill-and-mcp entry in the DeFi section and its link target.

Important Files Changed

Filename	Overview
README.md	Adds two Meteora entries — one in the DeFi skills section and one in Developer Tools — both pointing to the same URL (https://docs.meteora.ag/mcp); the DeFi skill entry also introduces inline Markdown links in its description, inconsistent with every other entry in the file.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[README.md] --> B[DeFi Section]
    A --> C[Developer Tools Section]

    B --> D["meteora-ai-skill-and-mcp\n(new — line 44)\nhttps://docs.meteora.ag/mcp"]
    B --> E["meteora-skill (existing)\nhttps://github.com/sendaifun/skills/…/meteora"]

    C --> F["Meteora Documentation MCP\n(new — line 98)\nhttps://docs.meteora.ag/mcp"]

    D -. "same URL" .-> F

    D --> G["DLMM docs + dlmm-sdk"]
    D --> H["DAMM v2 + damm-v2-sdk"]
    D --> I["Dynamic Bonding Curve + dbc-sdk"]

Loading

_{Reviews (1): Last reviewed commit: "docs: add Meteora AI tooling" | Re-trigger Greptile}

[greptile-apps]

DeFi skill entry links to the same URL as the Developer Tools entry

Both meteora-ai-skill-and-mcp (line 44, DeFi section) and Meteora Documentation MCP (line 98, Developer Tools) resolve to https://docs.meteora.ag/mcp. Every other entry in the DeFi skills section links to an actual skill file or repository (e.g. the adjacent meteora-skill links to https://github.com/sendaifun/skills/tree/main/skills/meteora). If this entry is meant to represent an AI coding skill, it should link to the skill's source or installation page — otherwise readers following the DeFi entry will land on the same documentation MCP page they would find under Developer Tools, making the DeFi listing redundant.

[greptile-apps]

Inline Markdown links in description break list style convention

This entry embeds six hyperlinks inside its description prose ([DLMM](…), [dlmm-sdk](…), [DAMM v2](…), [damm-v2-sdk](…), [Dynamic Bonding Curve](…), [dynamic-bonding-curve-sdk](…)). Every other entry in the file uses plain text (or inline backticks for package names) with only the lead link in the [name](url) heading slot. The heavy linking makes this entry visually inconsistent and harder to scan; the SDK GitHub URLs could be moved to the Developer Tools entry or trimmed to a single canonical link per product.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!